5 ms·
It was SOA (Service Oriented Architecture) where you would split them up, that predates Microservices by quite a bit. I remember doing that in the early 2000s.
by Clubber 5y ago
It was SOA (Service Oriented Architecture) where you would split them up, that predates Microservices by quite a bit. I remember doing that in the early 2000s.
What I think he is saying is that Microservices people pitch their service against monolith as better, but monolith hasn't been in vogue for 20 years. I saw the same tactic with scrum people pitching against waterfall which hadn't been in vogue for quite a while either.
- deleted 5y ago[deleted]
- deleted 5y ago[deleted]
- hdjjhhvvhga 5y agoWell, SOA is such a broad term. If you include CORBA, you could say it's terrible. On the other hand, gRPC is a pleasure to work with if you need to deal with different environments.
- xtracto 5y ago> On the other hand, gRPC is a pleasure to work with if you need to deal with different environments. I remember doing RPC via Java RMI and Jini at some point early in my career in the late 90s. It was really nice and gRPC reminded me of that.
- jbverschoor 5y agoAlthough clunky to implement, EJB had really well thought out concepts, architecture and roles
- pjmlp 5y agoI miss dealing with Websphere every time I am fixing Kubernetes spaghetti.
- throwaway894345 5y agoThe OP was pretty explicitly arguing in favor of monolithic architecture. > The term "Monolith" was devised by people who wanted to brand microservices as newer and superior. It's almost as if in order to succeed these days you need to discredit and disparage your competition rather than simply having a better product, and that's why I don't buy into buzz words at all.