Making Smart Async Architecture Decisions: Patterns, Trade-offs
Details
IMPORTANT: Participants must register through the registration link
Shortlisted candidates would receive a confirmation a few days prior to the event. As we have limited seats, registration is mandatory, and we recommend registering soon.
Designing Asynchronous Systems: Choosing the Right Pattern for the Problem
“We started with a message queue. Then added events. Then introduced orchestration. Now nobody is quite sure why the system works the way it does.”
Sound familiar?
Asynchronous communication is one of the most powerful tools in distributed systems. It helps us decouple services, improve scalability, and build resilient architectures. Yet many teams find themselves struggling with a different challenge: deciding which asynchronous pattern is actually the right fit for the problem they’re trying to solve.
As requirements evolve, architectures evolve too. The challenge is that there is no universal answer. The same requirement can be solved using different approaches, each with its own trade-offs. What works well today may introduce unnecessary complexity tomorrow—or fail to support future business needs altogether.
What You’ll Do in This Session
This is not a presentation about Kafka, workflow engines, or any specific technology.
Instead, participants will work through a realistic business scenario and collaboratively design solutions as requirements evolve.
Throughout the workshop, you will:
- Evaluate different asynchronous communication approaches for the given business problem
- Make architecture decisions based on changing requirements
- Explore the trade-offs between messaging, events, workflows, and orchestration
- Discuss how requirements such as ordering, retries, compensation, and auditability influence design choices
- Refactor architecture decisions as new constraints emerge
Core Idea
👉 Architecture should be driven by behaviour and business requirements, not by technology trends.
Rather than asking “Should we use Kafka?” or “Do we need a workflow engine?”, we’ll learn to ask:
- What behaviour does the system need to support?
- What guarantees are required?
- What trade-offs are we willing to accept?
- What is the simplest solution that satisfies the requirements?
By focusing on requirements first, architecture decisions become clearer, more intentional, and easier to evolve.
What You’ll Walk Away With
- A practical framework for evaluating asynchronous communication patterns
- Better intuition for choosing between messaging, events, workflows, and orchestration
- A deeper understanding of the trade-offs behind common async architectures
- Techniques for avoiding both under-engineering and unnecessary complexity
- Greater confidence in making architecture decisions as systems evolve
“Not every async problem needs Kafka. Not every event needs a workflow engine. Not every workflow needs orchestration. Architecture should evolve based on requirements, not trends.”
🎤 Facilitators
👩🏫 Sneha Bagri
Solution Consultant at Sahaj Software
Tech enthusiast who loves architecting systems that are clean, scalable, and easy to live with. She enjoys breaking down complex problems and turning them into simple, reliable solutions.
👨🏫 Ponnala Abhinav
Solution Consultant at Sahaj Software
Software Engineer focused on backend development, distributed systems, and cloud-native applications. Focused on problem-solving and creating clean and effective solutions.
👨🏫 Vishnuvardhana Reddy Kareti
Solution Consultant at Sahaj Software
Over the past 15+ years, he worked across backend development, delivery of cloud-native products, collaborating closely with cross-functional teams and driving software development best practices
Event Details
- Date: Saturday, July 4th, 2026
- Time: 09:30 AM – 01:00 PM (IST)
- Location: Sahaj Software Office
- Format: Interactive architecture workshop with collaborative design discussions and requirement-driven system evolution
Who Should Attend
- 5+ years of hands-on experience
- Fundamentals in System Design, Architecture and Asynchronous communication patterns
- Interest in building large scale, reliable and systems
👉 Important Registration Notice
- All registrations will be waitlisted initially
- Only official confirmation email guarantees entry
- Meetup/platform emails are not confirmation