My Authors
Read all threads
I worked on several migration projects from SOAP services to microservices back in 2007-2010. We have done a lot of mistakes by following the hype instead of doing what was best for us. (a thread)
We assumed sizing things small without understanding their impact on the organization and operation was the best practice. We had little experience operating a large number of services and didn't quite understand what will scale and what won't scale.
protobuf and similar were not available back then. And we didn't have resources to designate a single RPC standard for the entire organization. It was patches of things everywhere. Some were RESTful endpoints, other teams invented their own JSON-RPC and binary-RPC protocols.
It was a mess. There was not an easy way to discover the existing services. There was no easy way to discover what's available from the services. The client story was quite depressing too. Most teams were using Java (and some did C++ and C#) and built their half baked solutions.
I said there was no consensus on the RPC protocol, right? Some were too smart and started add message queues in between services!!! So they redesigned the overall system and converted a bunch of stuff from sync to async for the convenience of MQ libraries. What a facepalm.
There was absolutely no visibility into the critical path. We were grepping a bunch of logs here and there to see why things fail and why they succeed. It was easily the top catastrophe I've ever seen in my career yet almost everyone was assuming this is how you do microservices.
Then, each team discovered the joy of ownership and how much authority opportunities there are. Microservices started to become very small. We created more work by adding more complexity and created "more jobs" by building a system that was 10x more complex. What a total win!
Missing some Tweet in this thread? You can try to force a refresh.

Enjoying this thread?

Keep Current with Jaana Dogan

Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!