Controlling Fanout in Event-Driven Architectures
Event fanout is powerful, but unbounded fanout causes chaos. Techniques: TTL + retry caps in queue handlers De-duplication with event IDs Throttling subscriptions via fanout controllers A...
Event fanout is powerful, but unbounded fanout causes chaos. Techniques: TTL + retry caps in queue handlers De-duplication with event IDs Throttling subscriptions via fanout controllers A...
When working on federated GraphQL systems, reusing schema fragments becomes crucial. Tips: Use custom schema printers to extract and reuse Modularize common types like PageInfo, Error, Metada...
Spent time diving into RxJava. Insights: Observable pipelines feel clean and concise Great for streaming data and async workflows Debugging can be tricky — use .doOnNext and Schedulers.tram...
JMeter is still my go-to tool for stress testing REST APIs. Benefits: Thread group-based concurrency control CSV data sources for realistic simulations Easy visualizations and plugins Sam...
Hystrix was the go-to for circuit breakers, but limitations surfaced quickly. Alternatives emerging: Resilience4j (lighter, modular, Java 8+) Envoy for service mesh-level resilience Custom ...
In any retry-prone system — payment gateways, provisioning services, async job queues — idempotency is your safety net. Patterns: Client-generated UUIDs Idempotency keys with deduplication st...
tmux became a key part of my terminal workflow this quarter. Key bindings: ctrl-b % to split vertical ctrl-b o to move between panes Sessions persist even if SSH drops tmux layout Grea...
Finally got my hands dirty with GraphQL. Initial impressions: Query exactly what you need = less overfetching Schema introspection is powerful Works best when you think about data as a grap...
Hystrix provides a real-time metrics stream that feeds directly into dashboards. Setup: Expose stream endpoint: /hystrix.stream Plug it into Hystrix Dashboard Watch circuit status, thread p...
Code reviews are my favorite ritual. Here’s a living checklist I use: Does it solve the original problem? Can I understand the changes without reading the Jira ticket? Tests: present and me...