You have to choose good defaults. For some systems, that's fail open. For others, it's different. I'd also begin to ask "are there solutions that are futher upstream and/or lower on the OSI model where we could handle this level of overwhelm?"
https://stanza.systems is a managed thing that offers this functionality (and a bit more) if y'all are looking for an escape valve away from redis as the coordination mechanism.
Location: Portland, OR
Remote: Yes, hybrid in PDX is fine.
Willing to relocate: No
Technologies: Go, Python, Rust, Java, Javascript/Typescript, AWS, Kubernetes, etc
Résumé/CV: https://justin.abrah.ms/resume.pdf
Email: justin@abrah.ms
Hey folks.
I care a bunch about engineering efficiency, shipping products that customers like, and generally being a helper. I've been serving as a principal engineer for Fortune 500 companies for the past few years and I appreciate how that role allows me to help lots of folks get better at their job.
A role will probably be a good fit for me if:
- the team wants to be better tomorrow than they are today (always learning / improving)
- customer happiness/delight is a priority to the company
- there is a clear direction for "success" (even if we might not yet know how to get there) and some way to measure if we've gotten there (even if that measurement might change over time)
I feel especially capable at helping you with:
- cross-organizational initiatives
- fundamental technology shifts and the reducation/replatforming that it requires
- iteration of a legacy/needs-some-love code base towards a more maintainable place
- open source strategy / involvement
My experience w/ most news outlets is that they have a random article I'm linked to. That's not worth a subscription in my mind. A news service you have an ongoing relationship with is.
Mobile phones have less powerful CPUs. Parsing large json objects and then building up a corresponding html structure may be more difficult than on the server (where you already have it loaded into memory anyway).
I always see these claims but isn't network the more limiting factor?
Or do people study this while thinking about IoT which may use more limited resources while still relying on the internet?
Especially since a server has to handle multiple request concurrently, it doesn't seem to be remotely the same workload that a single device CPU would see anyway?
I can't speak to any kind of general principle here, but viewing any standard modern web page e.g. Twitter, Discord in a Web browser reliably takes more CPU and memory than running a late-game Factorio save.
I will allow that it is probably theoretically possible to do client-side rendering in a CPU-efficient way, but it sure isn't the standard.