Introducing deliberate architectural practices into existing monolithic codebases can be daunting. Often the code itself can resist such attempts in subtle ways that negatively impact a team with little architectural experience.
Drawing on a real-world project as an example, James Thompson explains how to implement bounded contexts into such applications in conjunction with normal feature development and maintenance. Emphasis will be given to the aspects of the application that made implementing better architectural practices more difficult, including matters of process and implementation. Along the way, James shares a feature that provides the practical vehicle for introducing architectural improvements to one area of the application and discusses how this feature was used to bring more deliberate architectural thinking and boundaries to the example project.
James Thompson is a staff software engineer at Nav, where he is committed to helping engineering teams become more deliberate in how they build software through developing strong learning cultures, principled engineering practices, and holistic architectural thinking. He has worked with web technologies since 2003. He also loves barbecue.
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