3 ms·

microservices I take it ;-) ?

• jeffbee 3y ago
  Yes it was one of those extremely bad architectures where every little thing that could have been a library function was an RPC instead and all the services were running in containers with .1 CPU quota and 64MB of memory.
  • steveBK123 3y ago
    Someone needs to explain to me the purpose of containerizing architecture down to such small subcomponents that they could have run on my Windows 98 machine 25 years ago. At some point you're wasting a lot of time/bandwidth on RPC, and/or memory on all the data copies across process boundaries. So its bigger and slower, harder to orchestrate, harder to monitor, and.. I'm sure there's some positives somewhere.
    • jeffbee 3y ago
      I don't get it either, and the people who designed and built that system were idiots, so I didn't get a good impression of such fine-grained services. I am comfortable with services that are much larger, such as "store this document" or "classify an email as spam or not".