-
1/ If you tell people that a good bounded context matches one subdomain and, therefore, it should be one Microservice. You will have as many bounded contexts as Microservices. #TechDriven Worst case scenario, you will have Entity Microservices and a lot of context mapping.On twitter.com
❤️ 2 Favorites Mood 0
-
2/ Indeed, the service to service REST calls is what it's valuable for the business! Context Mapping will show a lot of coupling, surfacing a deficit on Design based on Business. Yet, feeling that we did good bounded contexts, far from reality 😓Permalink On twitter.com
-
3/ The good part is that, when we have Entity Microservices. The business logic can be found in the BFFs or GraphQLs as Queries and Mutations. Given a point, there's a central Microservice orchestrating all the service calls. Best case scenario, you can use them to identify BCPermalink On twitter.com
