Content ππ½οΈ
Designing architecture with EventStorming and Bounded Contexts (by Fabrizio Di Napoli)
The Efficiency Paradox: How being less busy can deliver more value (by Ekaitz Hernandez)
Context Mapping with Team Topologies (by Younès Zeriahi, Fabrizio Di Napoli, DamiÑn Blanco, Tiago Costa, Lucas Moreyra, Sol Latorre, Ekaitz Hernandez and Aleix Morgadas)
Identifying Core Domains (by Younès Zeriahi, Fabrizio Di Napoli, DamiÑn Blanco, Albert Llousas, Tiago Costa, Lucas Moreyra and Sol Latorre)
Discovering Bounded Contexts (by Younès Zeriahi, Fabrizio Di Napoli, DamiÑn Blanco, Albert Llousas, Tiago Costa, Ivan Gonzalez and Sol Latorre)
Domain-Driven Design Roundtable (by Younès Zeriahi, Fabrizio Di Napoli, DamiÑn Blanco and Albert Llousas)
Hands-on domain discovery with Event Storming (by Younès Zeriahi, Fabrizio Di Napoli, DamiÑn Blanco, Albert Llousas and Tiago Costa)
Innovation Impacts: Successful Business, Social, and Technical Investments (by Vaughn Vernon)
Systems Thinking by combining Team Topologies with Context Maps (by Michael PlΓΆd)
PresentaciΓ³n del Curso de Fundamentos de EventStorming (by Daniel SolΓ© Morera)
EventStorming Fundamentals Course Presentation (by Daniel SolΓ© Morera)
What Really Matters (by Jimmy Nilsson)
Panel discussion about EventStorming (by Daniel VΓ‘squez, Angel Costela Sanmiguel, Henrique Ribeiro Rezende and Daniel SolΓ© Morera)
Big Picture EventStorming on Glovoβs Machine Learning Workflow Cycle (by Amir Hossein Bakhtiary Davijani and Daniel SolΓ© Morera)
Reactive DDD - Transforming Digital Business (by Vaughn Vernon)
Event Storming: modelling processes and services + modelling software systems (by Daniel SolΓ© Morera)
Modelling business processes with Event Storming (by Daniel SolΓ© Morera)
From ddd to DDD. My journey from data-drive development to Domain-Driven Design (by Thibaud Desodt)
Event sourcing and CQRS: lessons from the trenches (by David JimΓ©nez MartΓnez)
Reactive DDD - When Concurrent Waxes Fluent (by Vaughn Vernon)
Why you should use Domain StorytellingΒ (by Daniel SolΓ© Morera)
Adopting Domain-Driven Design in your organization (by Aleix Morgadas)
The fallacy of global state reconstruction from event storage (by Jordi MartΓnez SubΓas)
How practical Event Storming uncovers Domain-Driven Design strategic design (by Daniel SolΓ© Morera)
Facilitating Event Storming (by Daniel VΓ‘squez)
Tackling the technical test as a domain problem (by Eduard SimΓ³n Gallegos)
Theoretical and Practical Event Storming (by Daniel SolΓ© Morera)
Divulgar el concepto de DDD desde jΓΊniors a sΓ©niors por reciclar sin desfallecer en el intento (by Fernando Aparicio Reviriego)
Activity
Call For Proposals (CFP)
Send your Call For Proposal (CFP) at hi@dddbcn.org or a direct message (DM) to @dddbcn, @dsolemorera or contacting the organiser usingΒ Meetup.
Formats
- Live coding
To any DDD related topic, would you like to...
share and discuss about your implementation?
share your approach to solve a problem?
conduct step by step your implementation and transformation journey between two points in code?
transforming functional requirements into code?
any other option involving codeΒ
2. Workshop (practical/hands-on)
Participant:
take part for the first time?
feel again the power and magic of learning taking action collaboratively and discovering new opportunities?
have a suitable and safe place to experiment with no constraints and with all the needed material?
Domain expert:
explore a domain you know well and be it the working example of the workshop?
explore the domain of a project you {are working on / are planning to work on} but you haven't had the chance to use any of the tools or techniques?
Facilitator:
help with a proper development of the workshop (and also take part if desired)?
All:
get the outcome of the workshop and learning experience?Β
3. Panel/Open discussion, questions & answers (Q&A) or fishbowl conversations
- Do you have any DDD related question you do not know how to address?
- Would you like to propose a discussion about an available recorded talk in a previous conference or about some specific chapters or pages of a DDD book?
Send us your proposals filling out this form:
4. Talk
1. Some examples of a talk might be:
- Introduction to DDD: what it is, when to apply it, strategic design, tactical design
- Your experience applying DDD in a project
- Microservices and Bounded Context
- Domain Modelling
- Domain Storytelling
- Event Storming
- How to determine aggregates?
- When and why apply CQRS?
- {hexagonal / onion / ports & adapters} architecture within DDD
- When to use Event Sourcing?
- Refactoring legacy code with a DDD approach
- Functional programming and DDD
2. The following are the types of talk duration to fit in:
- Mini talk: 5 up to 15 minutes
- Small talk: 15 up to 25 minutes
- Medium talk: 25 up to 35 minutes
- Long talk: 35 up to 50 minutes
- Hero talk: 50 up to 90 minutes
Mini and small talks are your option if:
- It is your first talk.
- You would like to explain your solution addressing a problem with DDD.
- You would like to talk about a really specific DDD aspect.
At the end of each talk 5-10 minutes for questions if any are kept.Β