[maxxxxx]

A lot of people don't have the discipline to write decent libraries so they need the overhead of microservices to force them to structure their code reasonably. It seems to me you can have exactly the same boundaries between components that you get through microservices by just having a good compenent separation.

[tiziano88]

I feel 100% like you. Most developers won't think about clear interfaces between components unless they are forced to do so by an RPC layer. I think at some point we are going to realise this and step back on our footprints , ending up with a monolithic architecture with clearly defined boundaries between components enforced by expressive type systems.

[mgkimsal]

> Most developers won't think about clear interfaces between components unless they are forced to do so by an RPC layer.

The developers I know who can't think about clear interfaces are also the ones that won't know how to write clear RPC, and won't be able to create clean microservices.

[maxxxxx]

But they will have "microservices architecture" which looks better on your resume than monolith.

[eropple]

This is exactly true. And so is the reverse: competently written code can be segmented out into a SOA by replacing your internal procedure calls with a network call.

[Terr_]

Caveat: If it's acceptable to have significant latency or the interaction is asynchronous.

[eropple]

Sure, but if it's not acceptable to have significant latency then they're probably the same logical service, yeah?

[srtjstjsj]

if you have component separation, you have microservices