REST is very comfortable in a static domain model, where resources map to business entities, and standard HTTP methods describe state changes. But event sourcing and CQRS are now central to event-driven microservices, bringing a whole new perspective. Suddenly, events, not states, are the central focus. We’re challenged to reconcile this new, dynamic perspective with the static, data-centric view. But event-driven architecture isn’t just necessary for data consistency. As teams are discovering with event storming, this is a huge opportunity to construct a much more complete domain model that includes detailed data structures _and_ detailed change lifecycles. An “eventful domain model.”
In this session, Ted will show an experimental modeling language that binds data structures, commands, events, and REST APIs. We’ll explore a range of ways to adapt REST to an eventful domain model.
High impact blog posts and eBooks on API business models, and tech advice
Connect with market leading platform creators at our events
Join a helpful community of API practitioners
Can't make it to the event? Signup to the Nordic APIs newsletter for quality content. High impact blog posts on API business models and tech advice.
Nordic APIs will use the information you provide on this form to provide updates and news.
You can change your mind at any time by unsubscribing from any email you receive from us or by contacting us at info@nordicapis.com. We will treat your information with respect. By clicking below, you agree that we process your information per the terms in our Privacy Policy.
We use Mailchimp as our marketing platform. By clicking below to subscribe, you acknowledge that your information will be transferred to Mailchimp for processing. Learn more about Mailchimp's privacy practices.
Become a part of our global community of API practitioners and enthusiasts. Share your insights on the blog, speak at an event or exhibit at our conferences and create new business relationships with decision makers and top influencers responsible for API solutions.