Vaughn Vernon
From for { comprehension }
Vaughn Vernon is a veteran software craftsman and thought leader in simplifying software design and implementation. He has been programming since 1983, consults and speaks internationally, and has taught his Implementing Domain-Driven Design classes to hundreds of developers around the globe. Vaughn is the author of the 2015 best-seller "Reactive Messaging Patterns with Actor Model--Applications and Integration in Scala and Akka", best-seller "Implementing Domain-Driven Design", and his newest book "Domain-Driven Design Distilled", all three published by Addison-Wesley. Vaughn consults around DDD and Reactive applications using Akka.
Methodology & Culture
Reactive Microservices with DDD and Actors
What are microservices all about, and are they practical for your enterprise? How granular should a microservice be, and what approach should you use to determine the proper and appropriate boundaries between microservices? How can each microservice communicate with others in a distributed computing environment to correctly fulfill business objectives? How can my microservices adhere to the tenets of reactive software, being responsive, resilient, elastic, and message driven? Using Domain-Driven Design and Actors to implement microservices, this talk will demonstrate how you can create microservices while answering all of the questions posed, and more. The talk will show you how to carefully craft microservices and to model the business domain within. You will experience advanced use of the Actor model throughout.
Methodology & Culture
oDDs & enDs
(The title is a play on words, pronounced "Odds and Ends" but with the DDD letters emphasized. The summary of the presentation follows...)
The software development industry faces peril as entire teams are assigned to patch systems on a daily basis to keep them operational. Forget about DDD for a moment. What are some of the most insidious problems with software development today? Why do the same problems continue to happen across a vast array of corporate and software development cultures? After identifying the problems, how can DDD help teams overcome them? And, using DDD, what is a powerful approach to modeling your core domain while applying microservices? The current state of the industry incites a lot of questions, and you really should care about the answers.