For the record, at Uber, we're moving many of our microservices to what @copyconstruct calls macroservices (wells-sized services). Exactly b/c testing and maintaining thousands of microservices is not only hard - it can cause more trouble long-term than it solves the short-term.
- Microservices are hard. - Building reliable and testable microservices is a lot harder than most folks think - Effectively *testing* microservices requires a ton of tooling and foresight. - A Netflix/Uber style microservices isn't required by many (most?) orgs. - Macroservices?
92
1,048
292
2,977
Almost. First commit 5 years ago.
2
Strangely enough, that read like the definition of microservice architecture to me? Confused. Guess "right-sized" is the trick?
1