|
|
|
|
|
by larve
1322 days ago
|
|
(author here) This is a real difference, and one I want to expand on in my next article. You can fuck around much more in a web context than embedded, but you still often find out. Doing web "well" requires thinking in terms of realtime and memory constraints. I don't want the latency of my microservice to jitter, nor do I want it to use random amounts of memory. Not only will I be able to provision smaller machines, but I will also guarantee better SLAs. Building your microservice just like you would a hard realtime constraint (guaranteed memory usage per request, preferably no allocations at all, time guarantees (response within 50 ms or I fail) helps make a robust, performant and resilient web application. |
|