miggy

38 ms·

1.
When Reverse Proxies Surprise You: Hard Lessons from Operating at Scale(infoq.com)
101 points by miggy 10mo ago|11 comments
2.
Design Tradeoffs at the Edge(usenix.org)
2 points by miggy 1y ago|0 comments
3.
by miggy 1y ago
Scaling matters, but why pay for abusive clients or bots? Adding a cache is easy; the hard part is invalidation, sync, and thundering herd. Use it if the product needs it, not as a band-aid.
4.
by miggy 1y ago
We had a critical service that often got overwhelmed, not by one client app but by different apps over time. One week it was app A, the next week app B, each with its own buggy code suddenly spamming the service. The quick fix suggested was
5.
by miggy 1y ago
Excellent read. It highlights key aspects like health checks, server restarts, warm up, and load shedding, all of which make load balancing an already hard problem even harder.
6.
by miggy 1y ago
Willy from HAProxy has a good write-up on this. In their benchmarks, least-connections usually beat P2C, but P2C was never the worst and is arguably a saner default when least-connections isn’t available. The article link: https:/&#x
7.
by miggy 1y ago
A strong tooling ecosystem needs money, which usually means corporate sponsorship.
8.
by miggy 1y ago
Author here. Two quick thoughts: 1. As I covered in an earlier part of this series, service discovery is not always easy at scale. High churn, partial failures, and the cost of health checks can make it tricky to get right. 2. Using server-
9.
by miggy 1y ago
Author here. Absolutely, HAProxy’s sticktables is a powerful way to implement advanced routing logic, and they’ve been around for years. This series focuses on explaining the broader concepts and tradeoffs rather than diving deep into any
10.
by miggy 1y ago
Author here. Thanks for sharing these thoughts. You’re right that DSR, ASN-based routing, SRV records, and other lower-layer approaches are important in certain setups. This post is focused primarily on Layer 7 load balancing, connection an
11.
by miggy 1y ago
It seems HAProxy also added ACME/DNS-01 challenge support in haproxy-3.3-dev6 very recently. https://www.mail-archive.com/haproxy@formilux.org/msg46035.h...
12.
One network service policy architecture(infoq.com)
2 points by miggy 1y ago|0 comments
13.
Reverse Proxy Deep Dive: Why Load Balancing at Scale Is Hard(startwithawhy.com)
86 points by miggy 1y ago|10 comments
14.
by miggy 1y ago
Thanks for sharing this! I’m the author of the blog post. Happy to answer any questions about the scenarios in the article or dive deeper into specifics like slow start tuning, consistent hashing trade-offs, or how different proxy architect
15.
by miggy 1y ago
HTTP has never been truly simple, but HTTP/1.1 is probably the simplest it gets. HTTP/2 and HTTP/3 are significantly more complex.
16.
Seamless Istio Upgrades at Scale(medium.com)
1 points by miggy 1y ago|0 comments
17.
ChaCha12-BLAKE3: Secure, Simple and Fast authenticated and committing encryption(kerkour.com)
6 points by miggy 1y ago|3 comments
18.
by miggy 1y ago
One of the key aspects of feature flag systems is enabling A/B analysis, measuring the impact of features on metrics like click-through rate, session duration, and revenue. This doesn’t seem to be mentioned in the highlights. Is the pr
19.
by miggy 1y ago
A useful way to find ideas is by observing asymmetries. When something appears easy for some people but difficult for others, or vice versa, it often reveals underlying complexity, missing tools, or flawed mental models. Frustration can als
20.
by miggy 1y ago
In my experience, unit tests and logging code generated by LLMs tend to be overly verbose, miss meaningful assertions, and often produce boilerplate that looks correct but doesn’t test or log anything useful. It’s easy to get misled by the
21.
Reverse proxies handle service discovery at scale, and why it's so hard(startwithawhy.com)
2 points by miggy 1y ago|0 comments
22.
by miggy 1y ago
At my company, we went from using detailed RFCs to one-pagers, and eventually to writing no formal docs at all. Over time, RFCs turned into artifacts optimized for promotions rather than alignment or clarity. In many cases, people ended up
23.
Anatomy of a request: Beyond Backend Processing [video](youtube.com)
1 points by miggy 1y ago|0 comments
24.
Reverse proxy deep dive: Why HTTP parsing at the edge is harder than it looks(startwithawhy.com)
60 points by miggy 1y ago|13 comments
25.
Reverse proxy deep dive (2024)(startwithawhy.com)
93 points by miggy 1y ago|38 comments
26.
HAProxy and Couchbase Integration(medium.com)
2 points by miggy 1y ago|0 comments
27.
From startup to web scale: A gentle introduction to scaling
2 points by miggy 8y ago|0 comments