3 ms·
Uber is not reorganizing their microservices into "macroservices". The original tweeter refuted it, but it's still being propagated as fact. Granted the origina
by jennyyang 7y ago
Uber is not reorganizing their microservices into "macroservices". The original tweeter refuted it, but it's still being propagated as fact. Granted the original tweet was poorly written but in the thread itself, he refutes it later on.
- antoncohen 7y agoThank you. This is the core of it[1], IMO: > Back in the day, we’d spin up a microservice that did one, small thing just like that. We had a bunch of small services built and maintained by one person. This was great for autonomy, iteration speed, learning and making devops a no-brainer. You could spin up a service anytime: but you’d be oncall for it. > Now, as my area is maturing and it’s easier to look ahead, as we create new platforms, we’re doing far more thoughtful planning on new services. These services don’t just do one thing: they serve one business function. They are built and maintained by a team (5-10 engineers). They are more resilient and get far more investment development and maintenance-wise than some of those early microservceis. [1] https://lobste.rs/s/mc3k1c/at_uber_we_re_moving_many_our https://lobste.rs/s/mc3k1c/at_uber_we_re_moving_many_our
- kevindong 7y ago> We had a bunch of small services built and maintained by one person. That just seems like it'd be a disaster at any non-trivial scale.