James Ross discusses what concept maps are, how to construct one, what to do and what to avoid when creating one, and how to help a team build a shared mental model depicted in a concept map.
Chris Richardson discusses an event-driven microservice architecture, it’s benefits and drawbacks and how Spring Boot can help, implementing business logic using domain models written in Scala.
Ian Barber discusses the importance of behavior, domains and clarity of the names used when writing software or building systems.
Udi Dahan takes a look at why different kinds of pub/sub need to be used for specific domains like healthcare, finance, “internet of things”, and some kinds of retail.
Caoilte O'Connor explains how and when the Domain Service Aggregator Archetype can help, using the architectural evolution of "Video on Demand" in a broadcast company as a working example.
Mike Barker shares lessons learned at LMAX Exchange: starting from a clean domain model is imperative and understanding the trade-offs between performance and safety/generality/functionality.
Chung-Yeung Pang shares from his experience applying MDD and Agile to various projects.
Pedro Molina presents the challenges, benefits and limitations creating a cloud-based DSL tool. A demo of such a tool is included.
Volker Pacher, Sam Phillips present key differences between relational databases and graph databases, and how they use the later to model a complex domain and to gain insights into their data.
The authors share insights from their experience building DSLs for business people.
Michael Rauch and Christoph Gutmann explain how Eclipse Modeling technology is successfully applied to establish forward engineering in the domain of technical SOA.
Jürgen Mutschall ponders what is to be done to make MDSD a mandatory development methodology for every large scale project.