Re:Microservices – State of Developer Ecosystem 2022 (JetBra...
by dboreham on Thursday November 09, 2023 @12:00PM
(#38207565)
Silly me always thought Microservices was just a new word for SOA. What was the difference supposed to be?
[ Parent
| on HN ]
Re:Microservices – State of Developer Ecosystem 2022 (JetBra...
by miroljub on Thursday November 09, 2023 @12:37PM
(#38208107)
> Silly me always thought Microservices was just a new word for SOA.
Lucky you. You were using “Microservices” the right way all the time, without even realising it.
Re:Microservices – State of Developer Ecosystem 2022 (JetBra...
by zo1 on Thursday November 09, 2023 @01:21PM
(#38208692)
You've then been fortunate enough to have never worked at a place where something simple like a "join" requires a call to a separate service.
Suddenly something trivial becomes buzzword-filled chaos. Observability, apm, monitoring, kubernetes, scaling, events, pub sub, api contracts, Kafka, streams, multi repos, build pipelines, github workers, eventual consistency and so on.
Re:Microservices – State of Developer Ecosystem 2022 (JetBra...
by jugg1es on Thursday November 09, 2023 @02:34PM
(#38209866)
a capital 'M' microservice is a service that is entirely self-contained with its own datastore and everything. It's an architecture that makes sense if you are talking about the 'Orders' component of an e-commerce website but starts to get really weird if you need to share any kind of data between the microservices.