Re:Ask HN: Why do message queue-based architectures seem les...
by jupp0r on Wednesday June 19, 2024 @02:26AM
(#40725419)
If you are using Chrome, it's also a combination of multiple well separated processes talking via RPC with each other, which is pretty similar to microservices, although the separation boundaries are more influenced by attack mitigation requirements than your typical microservice architecture would be.
Re:Ask HN: Why do message queue-based architectures seem les...
by wg0 on Wednesday June 19, 2024 @02:58AM
(#40725591)
And even that process separation is spinning up more processes from within the same binary or build artefact. The usual fork() and CreateProcessW() etc and then wait on them.
Unlike in Microservices where each process is possibly a totally different language, runtime and framework spun up individually that too possibly in totally different ways.
Re:Ask HN: Why do message queue-based architectures seem les...
by kaba0 on Wednesday June 19, 2024 @04:22AM
(#40726073)
But that’s due to security, not for any supposed benefit of microservices. Also, both processes are from the same repo sharing code, so I wouldn’t really qualify as microservice.
Re:Ask HN: Why do message queue-based architectures seem les...
by jupp0r on Wednesday June 19, 2024 @12:15PM
(#40729652)
1. microservices also create security boundaries
2. microservices living in monorepos is common
Re:Ask HN: Why do message queue-based architectures seem les...
by Noneofya on Sunday June 23, 2024 @11:29AM
(#40768154)
That‘s literally an example of the decision depending on multiple factors. Separation of concerns -> more isolation -> stronger security of the overall system is exactly one of the possible benefits of microservices.
Scale is just one. There is also fault tolerance, security, organizational separation (which can be, up to a point, also be realized with libraries as you suggest), bigger ecosystem to choose from, …
If anyone doubts that, this very browser used to read and write is built all the way up with dozens of libraries from compression, network, image encoding, decoding, video encoding decoding, encryption, graphics, sound and what not where each library is totally separate and sometimes was never intended to be used to build web browsers by the original authors.
Rest assured, most of the business (or web 2.0 systems, search, curate, recommend, surface etc kind of) systems are a lot more simpler then an A class browser.