He says while working in his Monorepo that's service oriented.
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Exactly how are these two things different other than their name and who understands them?
-
Probably service size and loose wire coupling are the biggest difference to ejb style SOA (of course, we’re old enough to remember SOA before that, and afaik, there is no difference)
- Još 4 druga odgovora
Novi razgovor -
-
-
There were things that got aligned with SOA that broke down at scale(ESB, cross service transactions) if we’re saying that’s now solved then maybe? Conways Law still a huge blocker though..
-
I mean, squint hard enough and envoy is an ESB...
- Još 2 druga odgovora
Novi razgovor -
-
-
Microservices = SOA with more principals. It isn't an over correction imo, it's just that when you give people very broad concepts like SOA they don't know what to do with that. Microservices give you terminology and approaches to follow.
-
Eh - in all the cases, there were always principles. For example: it's not a service that stands alone until it has more than one caller. This is good advice, micro services or no.
Kraj razgovora
Novi razgovor -
-
-
Maybe? The important decision to make is when should you introduce a network boundary? Hard to give a clear prescription for this, as with most things "it depends" and requires experience and learning.
-
100%
Kraj razgovora
Novi razgovor -
-
-
I've been doing this so long that it's all just a blur of fad and backlash. SOA, Monoliths, microservices, it's all just endless arguing over the "right" way to write software and it's never going to be a thing that's "right" for 100% of devs no matter what "it" is.
- Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.