Read on Twitter
Wow this article from Dropbox on why @EnvoyProxy shines has tons of super 
takes: A thread covering security, concurrency, opencore 1/7
The hottest take was probably:
“writing modern C++14 is not much different from using Golang or, with a stretch, one may even say Python.” https://twitter.com/mattklein123/status/1288884133704286208
takes: A thread covering security, concurrency, opencore 1/7The hottest take was probably:
“writing modern C++14 is not much different from using Golang or, with a stretch, one may even say Python.” https://twitter.com/mattklein123/status/1288884133704286208
Still remember the days when @mattklein123 claimed “developer productivity was one of the highlights of modern C++” when introducing Envoy and people raising eyebrows at this claim.
Receipt: https://twitter.com/mattklein123/status/793982852694016000
Receipt: https://twitter.com/mattklein123/status/793982852694016000
2.
- goroutine-per-request” model and GC overhead greatly increase memory req in high-connection services.
- thread per request model allows better security than pre-forking servers (Nginx, unicorn, gunicorn etc.)
PS @mattklein123 any plans for adopting io_uring in envoy?
- goroutine-per-request” model and GC overhead greatly increase memory req in high-connection services.
- thread per request model allows better security than pre-forking servers (Nginx, unicorn, gunicorn etc.)
PS @mattklein123 any plans for adopting io_uring in envoy?
3. “Bazel is one of the best things that ever happened to our developer experience. It has a very steep learning curve and is a large upfront investment, but it has a very high return on that investment: incremental builds, remote caching, distributed builds/tests, etc.”
4. The post claims Webassembly is effectively going to be the de facto standard for all forms of “edge compute”.
Hard to argue with that, given the direction the largest edge platforms (CDNs duh) are taking.
I predict in maybe 4-5 years time.
Hard to argue with that, given the direction the largest edge platforms (CDNs duh) are taking.
I predict in maybe 4-5 years time.
5. Not exactly an advertisement for the open-core model of nginx (and let’s face it, pretty much ever opencore project has incidents that play out like this, most notable elastic).
6. As early as 2017, I raised the issue about the need for caching in envoy.
See this https://twitter.com/copyconstruct/status/936411055923662849?s=21
Nginx started as a web server and evolved to be the standard issue reverse proxy. No
Envoy started out explicitly as a ... sophisticated, hackable L4/L7 proxy.
See this https://twitter.com/copyconstruct/status/936411055923662849?s=21
Nginx started as a web server and evolved to be the standard issue reverse proxy. No
Envoy started out explicitly as a ... sophisticated, hackable L4/L7 proxy.
7. Observability is the most important operational need of ... any piece of software!
Amen!! If there’s one good trend above all that envoy has ushered in, let it be the need for APIs for everything, especially operational sine qua nons like stats, runtime config etc.!
/ FIN
Amen!! If there’s one good trend above all that envoy has ushered in, let it be the need for APIs for everything, especially operational sine qua nons like stats, runtime config etc.!
/ FIN
