Regarding microservices. They sound nice in theory, and certainly work for some cases. But what is the common pattern to handle a situation like this (in a performant and &quot;scalable&quot; way).<p>Say you have two (completely separate micro-) services:<p>- Order service
- Customer service<p>Now when a customer buys something, it is stored in the order service. But how is the customer information referenced in the order service? Do you store just some &quot;customer id&quot; and let the clients of this service worry about what it means? Or do you store some customer information also in the order service (in memory cache or in the services own datastore, both solutions which then need to synchronize this data somehow)?<p>Eg. how about a situation where you want to display a sortable list of orders, and it includes the columns for the customers first and last names. How can you sort on these columns if the order service doesn&#x27;t know anything about the customer other than some &quot;identifier&quot;? Especially if the list is paged so you can&#x27;t look up all the needed customer&#x27;s information.<p>Just thought about this because this article (and many others) tout microservices as some kind of silver bullet.