Please log in to watch this conference skillscast.
Event sourcing offers you many benefits from both business and pure programming angles. As it's such a fundamental design principle, one might argue that it should be introduced early in your designs. However, this doesn't need to be the case. Especially, when you are anticipating future requirements to be based on this but you don't have a budget to solve them yet as you are dealing with today's problems.
Join Tugberk in this session where he will walk you though an evolvable software architecture based on Domain-driven Design and CQRS, which can let you optimise for today's problems at the same time allowing you to design towards event sourcing. You will also start understanding the concepts of Hexagonal Architecture pattern, which puts the Domain at the heart of the system and pushes the input and output at the edges.
This talk will give you some techniques to let you be tactical about your architectural approach, which will be especially handy when conflicts arises between business needs and refactoring costs.
YOU MAY ALSO LIKE:
- Getting Into the Zero Downtime Deployment World (SkillsCast recorded in June 2019)
- Microservices Architecture with Jorge Ortiz‑Fuentes (Online Course on 15th - 17th February 2021)
- Sociotechnical Domain-Driven Design with Kacper Gunia (Online Course on 18th - 19th February 2021)
- μCon: The Microservices eXchange (Online Conference on 13th - 14th April 2021)
- DDDx — Domain-Driven Design eXchange 2021 (Online Conference on 8th - 9th June 2021)
- Evolutionary Architecture (SkillsCast recorded in January 2021)
- What an Architect Can Learn from Retrospective Failures (SkillsCast recorded in December 2020)
Designing Towards Event Sourcing
Tugberk is a self-motivated software developer who craves to create great software products and systems and build effective development teams with a decade of software development and technical leadership experience. He is passionate about knowledge sharing and has been trying to do his best by speaking at conferences, writing blog posts, establishing collaboration on open source projects, and authoring a book. He cares about reliability, observability and scalability of the software products he works on as much as caring about the day-to-day happiness, effectiveness, and productivity of the team he works as part of. He also aims to strive for the balance required to have a stable, maintainable and architecturally-accurate software product, and being on the market fast with an iterative approach.