Domain Driven Design Meetup #17
- Date
- 2026-01-15
- Location
- San Francisco, CA, USA
- Host
- Domain Driven Design - San Francisco Bay Area
About this event
If you care about building software that matches the real shape of the business, this meetup is for you. Domain Driven Design Meetup #17 brings together people who want better models, clearer boundaries, and more useful conversations about how complex systems actually get designed. Expect a thoughtful in-person evening in San Francisco with a community that values both technical depth and practical application. This is not a generic networking event where people trade buzzwords and move on. It is a gathering for people who want to talk seriously about domain modeling, architecture, collaboration, and the day-to-day decisions that make systems easier or harder to evolve. About the Event Domain Driven Design, at its core, is about making software reflect the language, rules, and realities of a domain. This meetup creates space for that conversation in a way that is social, grounded, and useful. Whether you are deep into DDD already or still figuring out how it applies to your work, the event is designed to help you connect ideas to practice. As the seventeenth edition of the meetup, this gathering is part of an ongoing community rather than a one-off event. That matters because recurring meetups tend to attract people who are genuinely invested in the topic: engineers, architects, product-minded technologists, and curious builders who want to keep sharpening how they think. The format is in person, which makes a real difference for a subject like this. DDD often lives in the space between code, architecture, product thinking, and communication. Conversations are richer when people can sketch ideas, compare experiences, and ask follow-up questions naturally. You can expect a balance of community connection and focused discussion. The goal is to create an evening where you can learn something concrete, meet people who think carefully about software design, and leave with a few stronger ideas than you arrived with. What to Expect The evening begins at 5:00 PM PST on Wednesday, January 14 in San Francisco. Since this is an in-person meetup, plan for the flow to feel more conversational and community-driven than a formal conference. That usually means time to settle in, meet people, and ease into the topic before deeper discussions begin. While the exact session details are not listed here, you should come ready for the kinds of interactions that make a DDD meetup valuable: Focused discussions around modeling, boundaries, language, and system design Community conversations with people working through similar technical and organizational challenges Peer learning through shared examples, lessons, and questions from real projects Informal networking that goes beyond introductions and gets into how people actually work Expect a room with mixed perspectives. Some attendees may be applying DDD in mature systems; others may be exploring it for the first time in the context of microservices, product development, event-driven systems, or team collaboration. That range is a strength. It gives the conversation practical breadth and keeps the event from becoming too narrow or abstract. Because this is a meetup rather than a highly scripted seminar, one of the most useful parts may be what happens between the formal moments. The side conversation after a session, the comparison of two approaches to boundaries, or the quick exchange about how a team handles shared language can be where the most actionable insights emerge. Why Attend If you have ever felt the gap between business language and system design, this meetup speaks directly to that problem. DDD gives teams tools for thinking more clearly about complexity, and being in a room with others who care about that can sharpen your judgment fast. You will likely leave with more than inspiration. Good meetups create traction. You may walk away with a better way to frame a modeling problem, a clearer question to bring back to your team, or a more concrete sense of how others are approaching architecture and collaboration. There is also real value in meeting people who share this mindset. Software design can be isolating when your day-to-day environment is focused only on shipping speed or tooling trends. A community built around DDD offers a different kind of conversation: one that takes domain understanding seriously and treats design as a craft. This event is also a strong fit if you want to build local connections in San Francisco around thoughtful engineering practice. The networking here is naturally filtered by interest, which means the people you meet are more likely to be relevant to your work, your questions, and the kinds of systems you care about building. Practical Details Location: In person in San Francisco, USA. The exact venue details are not included here, so be sure to check the event page or registration information for the final address and arrival instructions. Time: Wednesday, January 14 at 5:00 PM PST. Since it starts in the late afternoon, it is well suited for people coming after work and for anyone who prefers a weekday evening format with room for both learning and conversation. A few useful ways to prepare: Bring a couple of real questions from your work if you have them Be ready to introduce yourself in terms of what you build or what domain problems interest you Come open to both structured discussion and informal conversation Plan a little buffer time for arrival, check-in, and connecting with people before or after the main program If you are looking for a smart, local, in-person community around software design and domain thinking, Domain Driven Design Meetup #17 is a strong place to spend your Wednesday evening.
Who should attend
This meetup is for people who want sharper conversations about software design, domain modeling, and the real-world complexity behind modern systems. - You are a **software engineer** who wants to design systems with clearer boundaries, better language, and stronger alignment with business needs. - You are an **architect or technical lead** thinking about service boundaries, collaboration across teams, and how to keep complex systems understandable over time. - You work in or around **product and engineering collaboration** and want to better understand how domain concepts shape implementation decisions. - You are **curious about Domain Driven Design** and want a practical, community setting to hear how others apply it beyond theory. - You enjoy **meetups where the networking is relevant**, and you would rather talk about real system tradeoffs than generic tech trends. - You are based in the **San Francisco** area, or can attend in person, and want to connect with people who care about thoughtful engineering practice. If you want useful conversations, local community, and a stronger handle on how DDD shows up in actual software work, you will likely feel at home here.