3 ms·
This article is about microservices. If you are not at scale you might not need microservices in the first place. When data is distributed, one team/service ow
by namanaggarwal 6y ago
This article is about microservices. If you are not at scale you might not need microservices in the first place.
When data is distributed, one team/service owns user data and other tweets. It becomes not so trivial.
- AmericanChopper 6y agoThis particular article is about microservices, but there's plenty of ordinary business reasons that you may have some sort of asynchronous business process that runs across a distributed set of systems/teams/organisations, that do not relate to scale. I was working on a microservice recently (really it was a service-oriented architecture, but they seem to pretty much mean the same thing now), and it only processed around 10,000 transactions per day. But it almost had to be designed that way, due to the nature of the business processes it was supporting, and the systems it had to interface with.