Yes, it's also called a distributed monolith. Thank you everyone :)
-
-
Prikaži ovu nit
-
magic 1000! check out my mixtape "please don't implement microservices before you're sure you need them, honestly monoliths can be good" on soundcloud.
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
-
-
There is actually a use case for microservices in this use case, when they have different security needs - be it different credentials for 3rd parties, are internet facing (or not), are API servers or clients, etc.
-
Is there a reason you can't model that as either different URL spaces run by a single app, or multiple WAI/Rack/etc apps mounted in the same process?
- Još 5 drugih odgovora
Novi razgovor -
-
-
I'd add: if it cannot be put down without introducing failures in other parts of your system, then it is not a microservice. Or even more: if your "microservices" know about each other, about each other locations and aliveness then they are not microservices.
-
Hm, I dunno about the first one - i think it's legit to have a microservice be built on top of other microservices, and obviously losing a layer beneath you is going to cause problems. Definite yes to the second though - it's the two-way relationship that's the problem.
- Još 6 drugih odgovora
Novi razgovor -
-
-
corollary: if you can't picture a world where you derive real business benefit from deploying microservices independently, why are you bothering? Just engineer your monolith better... or something.
-
i am very much a monolith fan for exactly this reason. if you can't see yourself remixing microservices that are already there without restarting things, what's the point?
- Još 9 drugih odgovora
Novi razgovor -
-
-
A beer to this guy now!
-
*checks clock* 5:25 as good a time as any. Cheers!
- Još 5 drugih odgovora
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.