Re:Stop Doing Microservices
by capableweb on Tuesday February 07, 2023 @07:32AM
(#34691886)
That sounds exactly what I'm describing? What you're doing is not "microservices" (the pattern where most processes are split out, not just "heavy" processes), but splitting out heavy processes when needed, rather than by default.
That's not a full microservice architecture. It's using a few services. It isn't committing to microservices
Re:Stop Doing Microservices
by jaredcwhite on Tuesday February 07, 2023 @07:04PM
(#34701891)
That sounds like the Citadel pattern…not microservices in the truest sense of the word.
https://blog.appsignal.com/2020/04/08/the-citadel-architectu...
Our team write everything in the main server except tasks that choke up the main server. For example, we have a need to process many CSV files from users. We put this processing on Lambda and it can scale to hundreds of Lambdas at a time. Scaling our main server would be very uneconomical.
Latency is not a problem because these services usually live in the same datacenter and the latency is very little compared to the processing time.