Combined together, command query responsibility segregation (CQRS) and event sourcing form a powerful design for high-performance systems. In the last couple of years, more and more companies (especially in the financial industry) have turned to this strategy to evolve their core platforms. When implemented well, systems are in a better position to prevent data loss and scale different areas of the application. However, it requires a shift in mindset for most development teams, so architects and leads need to look for alternative solutions to successfully develop, deploy, and maintain these systems. Stacey Watro and Maria Gomez explore strategies and pitfalls for supporting CQRS and event sources systems in production, covering how to build resilient systems, approach monitoring, and more.
Stacey Watro is a software developer at Stride Consulting. At heart, Stacey is a math nerd who enjoys problem solving and challenging herself to expand her knowledge. Throughout her career, she has been given the opportunity to grow as a developer by working with different technologies and awesome technologists. Stacey holds a master’s degree in computational mathematics from Clemson University.
Maria Gomez is a market tech principal at ThoughtWorks in Barcelona. Over her more than nine years of industry experience, Maria has worked with many different technologies and domains, which has helped her lead teams and advise stakeholders in making the right technology decisions. She is also a speaker and an advocate for diversity and inclusion in the IT industry.
Help us make this conference the best it can be for you. Have questions you'd like this speaker to address? Suggestions for issues that deserve extra attention? Feedback that you'd like to share with the speaker and other attendees?
Join the conversation here (requires login)
©2017, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com