-
@niluspc microservice as the buzzword... cannot really tell what means micro, the software industry tried to define it and we failed so hard 🤣 I will try to share the situation so, we identified that we have business constrain that looks like a common aggregate likePermalink On twitter.com
Mood +2 🙂
-
@niluspc but the aggregate is distributed, we decided to create it in microservice 1, but we need the realtime data from microservice 2Permalink On twitter.com
-
@niluspc So, either we do a sync https call each time to microservice 2 to create the aggregate or we just reply the data via events and we store a replica of entity 2 in the microservice 1. It's an already solved problem in the industry, no issue so far.Permalink On twitter.com
-
@niluspc What's ending happing is that microservice 2 is being acting as a Entity Storage. DB over CRUD either via HTTP or AMQP protocol mainly to serve microservice 1. So, having them split adds more complexity and maintenance that actual benefits.On twitter.com
-
@niluspc So, the effort to join them ends being not worth, so we keep them separated and dealing with the maintenance consequences.Permalink On twitter.com
-
@niluspc Damn Nil, you made me really thing about the reasoning 🤣😅 Don't know if I have explained myself well enough 🤷Permalink On twitter.com