#Microservices

Cindy Sridharan

- 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

Dinesh Chandrasekhar

This is a great thread and viewpoint on how unwieldy #Microservices can be after a certain number defeating the very purpose of why they were created in the first place.

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 -

So, please, let's not compound the stupid by calling these things 'macroservices',You didn't understand microservices. Now you may be clearer that you built nanoservices. Well, learn that, and start building

Camille Fournier

Boy tweets like this make me (and I'm guessing anyone else who did services before the "microservices" trend) feel oldhttps://twitter.com/GergelyOrosz/status/1247132806041546754 Services have been a good idea for a long time,

Microservices: "We solved DLL hell by wrapping every binary with HTTP"Don't at me Narrator: Wait, but that doesn't solve th...Dev: Shut up You still get dependency hell, you still have

Jaana Dogan ヤナドガン

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

This morning, I've written a few things about the downsides of a microservice architecture. A thread Don't be a victim of the fallacies of distributed computing:- The network is

I'm developing a new alternative to microservices that addresses many of the problems that people run into. I call it "SPMSA". Bear with me -- I'll explain the acronym in

If you rewrite your entire backend in JavaScript, things will get much simpler and more stable. I mean, just look at how simple and stable is client side JavaScripHUWAHAHAHAHAHAHAHA sorry,

Jaana Dogan ヤナドガン

Most of the small companies I worked had 2-4 monoliths per project that split into 5-15 micro services as the projects grew. The difference between microservices and monoliths have always

Uber in 2016: “We have thousands of microservices.”Everyone: “That sounds insane."Uber in 2020: “It turns out that was insane.” https://twitter.com/sandofsky/status/1129083949752262656

Nicolò Marchesi

Monolith vs Microservices... which is best?The answer is... it depends! Follow the thread to know a little more about application architectural models and find out which one is for you.

Here's an introduction to the C4 model in a few tweets. The C4 model is a way to visualise the software architecture of a software system, and a way to

The real ORM mismatch:#hibernate (JPA) is great if you have a desktop dialog/wizard workflow where you edit something in 20 different places and hit save at the end.For #java REST/microservices,

Random thought: using interactors/actions classes isn't OOP. I guess it's OK if it's considered an outer layer of the application. OOP is about messages and objects: state and functions/methods combined