Miłosz Smółka

Hey @aschrijver, thank you for raising this. We share your concerns and will consider alternatives to the services we use. In regards to Firebase, the post's title might be suggesting...

Hey @timsolov! Thanks, it's great to hear the project is helpful. 🙂 What you mention is correct, these two places don't have consistent updates. We did this on purpose to...

Hey @davix, I'm glad to hear you like the articles. :) You're totally right, the current structure is not usual when working with microservices. We picked this way to make...

@msamoylov It's persisted in the `UpdateHour` method: https://github.com/ThreeDotsLabs/wild-workouts-go-ddd-example/blob/22c0a25b67c4669d612a2fa4a434ffae8e35e65a/internal/trainer/adapters/hour_memory_repository.go#L66 The result of `GetHour` is returned to the frontend application, which shows the hour as empty, if it's not filled in the...

Hey @frederikhors. Sure, there's no issue with using pointers to repositories or other adapters. In most cases, you would find the effect on memory negligible, though. In the example above,...

What error did you get? You will probably need to change some occurrences in the code to match pointers, but it should be straightforward.

Hey @jcorry! The reason is simply we didn't use gRPC this way yet. The gRPC gateway seems to totally make sense for the kind of communication we've created. On the...

Actually, adding gRPC gateway would be a great example of how Clean Architecture enables such changes. In Wild Workouts, it would be just extending the ports layer. :)

Hey @maranqz. I think I don't understand the context fully, but here's some thoughts: * Consider if all messages need to be part of the same aggregate. Keeping them like...

> I though there is a more elegant solution without creating many small methods on each operation. I would say it's a trade-off. :) You can have some sort of...