Loading...
Browse and manage your post history
## Why Event-Driven? Modern applications demand responsiveness, loose coupling, and the ability to scale independently. Event-driven architecture (EDA) delivers all three. Over the past two years, I've migrated three monolithic services to an event-driven model using **Amazon EventBridge**, **SQS**, and **Lambda**. Here's what I learned. ### The Core Pattern Instead of services calling each other directly, they emit events: ```typescript await eventBridge.putEvents({ Entries: [{ Source: 'orders.service', DetailType: 'OrderPlaced', Detail: JSON.stringify({ orderId, userId, items }) }] }).promise(); ``` Downstream services subscribe to the events they care about. This means: - **No coupling** between producer and consumer - **Independent scaling** — each consumer scales based on its own load - **Resilience** — if a consumer is down, events queue up and replay ### Lessons Learned 1. **Schema registry is essential** — without it, breaking changes cascade silently 2. **Dead letter queues save lives** — always configure DLQs for failed event processing 3. **Idempotency is non-negotiable** — events can be delivered more than once 4. **Observability requires investment** — distributed tracing across event boundaries is harder than HTTP calls ### When NOT to Use EDA Not everything should be async. Request-response patterns are still better for: - User-facing queries that need immediate results - Operations requiring transactional consistency - Simple CRUD with no downstream effects
Just finished reading this deep dive into event-driven architectures. The comparison between choreography and orchestration patterns is particularly insightful. Worth a read if you're designing distributed systems.
Curious to see where the community stands on serverless platforms in 2026. Which provider do you reach for first when building serverless applications?
Excited to share the creative process behind our latest brand identity project! From initial sketches to final deliverables, here's a glimpse into how we transformed a startup's vision into a cohesive visual language. Swipe through to see the evolution!
Just released the first episode of my new video tutorial series on building production-ready microservices with Kubernetes! This comprehensive guide covers everything from container orchestration basics to advanced deployment strategies.
The frontend landscape keeps evolving. Cast your vote — you can pick multiple frameworks you think will lead the pack this year!
In this week's episode, I sit down with leading AI researchers to discuss how artificial intelligence is reshaping the way we write, test, and deploy code. Listen to hear their predictions for the next decade of software development!
What an incredible first day at TechConf 2026! Here are some of my favorite shots from the keynotes, workshops, and networking sessions. The energy in the room was absolutely electric!
Missed my live coding session on code review best practices? No worries! Here's the full recording along with the slides and code samples. Learn how to give constructive feedback and improve your team's code quality.
Just wrapped up a deep dive into motion design for product interfaces. Here's a walkthrough of the key animation principles every designer and developer should know — timing, easing, choreography, and more.
Captured this incredible footage during our deep-sea expedition last week. These jellyfish produce their own light through a chemical reaction — one of nature's most beautiful phenomena.
This trailer still gives me chills every time. Being part of the crew that filmed John Florence across the globe was a once-in-a-lifetime experience. The ocean teaches you patience like nothing else.
## What Are TDRs? A **Technical Decision Record** (TDR) is a lightweight document that captures the context, options considered, and rationale behind a significant technical decision. Unlike ADRs (Architecture Decision Records), TDRs cover decisions at every level — from library choices to API design patterns to deployment strategies. ### Why They Matter Six months from now, someone (probably you) will ask: *"Why did we choose DynamoDB over PostgreSQL for this service?"* Without a TDR, the answer lives in: - Slack messages that expired - Meeting notes nobody can find - The memory of someone who left the company ### The Template I use a dead-simple format: ```markdown # TDR-042: Use SQS over Kafka for order processing **Status:** Accepted **Date:** 2026-01-15 **Deciders:** John, Sarah, Mike ## Context We need a message queue for async order processing. Expected throughput: 500 msgs/sec peak. ## Options Considered 1. Amazon SQS — managed, simple, pay-per-use 2. Apache Kafka — high throughput, event replay 3. RabbitMQ — flexible routing, self-managed ## Decision SQS. Our throughput doesn't justify Kafka's operational overhead. We don't need event replay for this use case. ## Consequences - No message replay capability - Limited to 256KB message size - Simpler ops, lower cost ``` ### Tips for Adoption 1. **Make it frictionless** — a Git-tracked markdown file, not a Confluence page nobody maintains 2. **Record the *why*, not just the *what*** — the decision is obvious in hindsight; the reasoning isn't 3. **Include rejected options** — knowing what you *didn't* choose is as valuable as knowing what you did 4. **Keep them immutable** — supersede, don't edit. History matters.
Looking for contributors to help build a real-time collaboration platform using WebSockets and React. The goal is to create an open-source alternative to existing tools.
We're looking for an experienced React developer to join our team for a 3-month e-commerce project. Remote work, competitive compensation.
We're building an open-source Kubernetes monitoring dashboard and looking for passionate developers to join! Skills needed: React, Go, Prometheus.
Seeking a talented UI/UX designer to collaborate on an open-source analytics dashboard. This is a volunteer project with potential for future paid work.
I've compiled the ultimate TypeScript cheat sheet covering types, generics, utility types, and advanced patterns. Free PDF download in comments!
What if AI could not just find bugs, but understand the intent behind your code and suggest architectural improvements? Here's my vision for the future.
I'm designing a REST API and wondering about versioning strategies. URL path vs headers vs query params? What do you recommend and why?
Cast your vote! React, Vue, Angular, Svelte, or something else? Let's see what the community prefers.
After deploying over 200 Lambda functions in production, here are the key lessons I've learned about cold starts, memory optimization, and error handling.
A decade ago, I wrote my first line of code. Today, I lead a team of 15 engineers. The journey has been incredible - from imposter syndrome to confidence.
We're hiring a Senior Full Stack Developer to join our growing team. Work on cutting-edge projects with React, Node.js, and AWS. Competitive salary and benefits.
I have 15+ years of experience and want to give back. Offering free 1-on-1 mentorship sessions for junior developers. DM me to apply!
Join us for the biggest developer conference of the year! 3 days of workshops, talks, and networking. Early bird tickets available now.
Excited to announce I passed the AWS Solutions Architect Professional exam! 6 months of preparation paid off. Happy to share study tips!
We're excited to announce real-time collaboration features! Now you can co-edit documents, share screens, and collaborate seamlessly with your team.
Monthly React meetup! This month we're discussing scalable architecture patterns. Pizza and drinks provided. RSVP required.
Controversial take: traditional code reviews are broken. Instead, we switched to pair programming and mob programming. The results? Faster delivery, better code quality.
I'm building an AI-powered learning platform and looking for a technical co-founder. If you're passionate about education and have experience with ML/AI, let's connect!
Many startups think design systems are only for big companies. I disagree. Here's why investing in a design system early can save you months of work.
A comprehensive list of Git commands every developer should know. From basics to advanced rebasing and cherry-picking. Bookmark this!
Starting a new project and debating architecture. We're a small team of 3. Should we go microservices from day one or start with a monolith?
Zero Trust isn't just a buzzword - it's a fundamental shift in how we think about security. In this guide, I break down the core principles.
Excited to announce that our new API documentation portal is now live! Check it out and let us know your feedback.
The great work debate continues! Share your preference and let's see where the community stands on work arrangements.
Join our fast-growing startup as a DevOps Engineer. Help us scale our infrastructure to millions of users. Equity included.
Struggling with your tech resume? I'm offering free resume review sessions this month. Limited spots available - sign up in comments!
Our open-source data pipeline library just hit 1 million downloads! Thank you to everyone who contributed and used it. This is just the beginning!
Can't make it to Vegas? Join our virtual watch party for AWS re:Invent keynotes. Live discussion and Q&A with AWS experts.
The future of digital identity isn't just about crypto wallets. I'm exploring decentralized identity systems that could revolutionize how we prove who we are online.
React Server Components are changing how we build web apps. In this deep dive, I cover the mental model, best practices, and common pitfalls.
Starting a new project to build a mobile app for managing community events. Looking for React Native developers and backend engineers.
Building a social platform with complex user relationships. Should I use PostgreSQL with proper relations or MongoDB for flexibility? Pros and cons?
Looking for an experienced Cloud Architect to design and implement enterprise-scale solutions. AWS/Azure certifications preferred.
We're building an open-source GitOps toolkit that simplifies Kubernetes deployments. Looking for contributors with experience in Go, Kubernetes, and ArgoCD.
Great documentation can be the difference between a product that gets adopted and one that gets abandoned. Here's how to treat docs as a first-class citizen.
After 3 years of hard work, I'm thrilled to share that I've been promoted to Senior Software Engineer! Grateful for my amazing team and mentors.
We've updated our community guidelines to ensure a safe and inclusive environment for all members. Please review the changes.
My startup failed after 2 years. Here are the honest lessons I learned about product-market fit, team building, and knowing when to pivot.
Starting a monthly virtual meetup for cloud architects! We'll discuss real-world architecture challenges, review designs, and share learnings.
After building production apps with both frameworks, here's my honest comparison. Performance benchmarks, developer experience, ecosystem maturity.
Join our research team working on cutting-edge ML models. PhD preferred but not required. Published papers a plus.
AI is transforming how we write code, but what about the rest of the developer workflow? I share my predictions for how AI will reshape debugging, testing, and deployment.
Playwright has become my go-to for E2E testing. This guide covers setup, best practices, CI/CD integration, and advanced patterns.
A comprehensive checklist for optimizing web performance. Covers Core Web Vitals, image optimization, code splitting, caching strategies.