GOTO Berlin is a vendor independent international software development conference with more that 60 top speakers and 600 attendees. The conference covers topics such as Java, Open Source, Agile, Architecture, Design, Web, Cloud, New Languages and Processes.
Eric Evans, TweetAuthor of Domain Driven Design
Biography: Eric Evans
Eric Evans is a specialist in domain modeling and design in large business systems. Since the early 1990s, he has worked on many projects developing large business systems with objects and has been deeply involved in applying Agile processes on real projects.
Out of this range of experiences emerged the synthesis of principles and techniques shared in the book "Domain-Driven Design," Addison-Wesley 2003.
Eric now leads Domain Language, Inc., a consulting group which coaches and trains teams to make their development more productive and relevant through effective application of domain modeling and design.
Software Passion: Breaking My Own Domain Models
Twitter: @ericevans0
Website: http://www.domainlanguage.com/
Books: Domain-Driven Design: Tackling Complexity in the Heart of Software
Presentation: TweetDDD and Microservices: At Last, Some Boundaries!
Microservices are associated with extreme isolation (e.g. no shared database, autonomous dev-ops teams, etc.) At its best, this creates a practical boundary within which modeling and design have a chance to thrive. In Domain-driven Design (DDD) we call this a "Bounded Context". Bounded contexts take many forms, some leakier than others, and the current best practices of microservices have given us perhaps the strongest mainstream manifestation of this principle to date. In this way, microservices can help teams who attempting DDD or other sophisticated approaches.Yet, as services get small and numerous, we might substitute one problem for another: The tangle of the monolith just migrates to become a tangle of interactions between microservices. Here, the strategic design principles of DDD can give architects a conceptual framework for working with suites of services and higher-level relationships between larger parts of systems.
This talk will introduce a few strategic design concepts and explain how they apply to development of microservices, as a tool for teams trying to grow large systems more coherently.
Workshop: DDD Overview Tweet
Location
This workshop gives you an overview on the basic principles and processes needed develop practically useful models, tie them into implementation and business analysis, and place them within a viable, realistic strategy.
Target: Architects, Experienced Developers, Analysts, Hands-on Technical Leaders
Suggested Prerequisites:
Some experience with projects developing complex software systems. Familiarity with iterative development processes.
Topics Introduced:
Morning: Ubiquitous Language & Model Discovery
- What is DDD?
- What makes a model useful to a software project?
- Cultivation of a model-based language to connect domain experts, developers, and the code itself
- Exploratory interaction of technical and business people in the modeling process
- Aggregates: A taste of rigor. This pattern addresses, at the model level, the scaling of systems in complexity, performance, and distribution
Afternoon: Strategic Design
- Distilling the Core Domain: Focusing fine modeling and design into those subdomains where the organization distinguishes itself
- Clarifying a shared vision
- Context Mapping: A pragmatic approach to dealing with the diversity models and processes on real large projects with multi-team/multi-subsystem development.
- Combining the Core Domain and Context Map to illuminate Strategic Design options for a project.