3 ms·
These two have resonated with me deeply. - Eliminated complex caching workarounds and data pipeline overhead - Simplified architecture from distributed system
by yilugurlu 1y ago
These two have resonated with me deeply.
- Eliminated complex caching workarounds and data pipeline overhead
- Simplified architecture from distributed system to straightforward application
We, as developers/engineers (put whatever title you want), tend to make things complex for no reason sometimes. Not all systems have to follow state-of-the-art best practices. Many times, secure, stable, durable systems outperform these fancy techs and inventions.
Don't get me wrong, I love to use all of these technologies and fancy stuff, but sometimes that old, boring, monolithic API running on an EC2 solves 98% of your business problems, so no need to introduce ECS, K8S, Serverless, or whatever.
Anyway, I guess I'm getting old, or I understand the value of a resilient system, and I'm trying to find peace xD.
- ramraj07 1y agoBut when were serverless systems like lambda and cloud workers "best practices" for low latency apis?
- hedora 1y agoAccording to their marketing material, when they started supporting running in edge pop's, they became the best option for low-latency APIs.
- daxfohl 1y agoLast I heard (~5 years ago), lambda@edge doesn't actually run on edge POPs anyway; they're just hooks that you can put in your edge configs that execute logic in the nearest region before/after running your edge config. But it's definitely a datacenter round-trip to invoke them. Adding that much compute to an edge POP is a big lift; even firecracker gets heavy at scale. And security risk for executing arbitrary code since these POPs don't have near the physical security of a datacenter, small scale makes more vulnerable to timing attacks, etc.