We live in a world of volatile requirements.
We’ve learned that big up-front design processes don’t work. You have to approach design incrementally so that you can incorporate lessons learned. Our designs are constantly under stress because they’re constantly changing.
Programs not designed to handle that stress will kill your project. Code that resists change slows you down so much that Agile processes will fail, no matter how well you execute.
A new approach to design is essential. Traditional n-tier architectures just don’t work in this environment, for example. The best way to handle volatility is to firmly ground your architecture in the domain and then implement it in a highly modular way where the modules really are independent. Microservices and messaging are integral to this approach, and systems developed in this way are scalable, robust, and well suited for deployment in a cloud environment.
Allen Holub leads a hands-on training covering the entire system design process, starting with planning strategies and “user stories” and ending with a full microservice-based implementation architecture. You’ll work on real-world problems that you bring to class rather than a pedagogic exercise.
Defining a story
Planning for uncertainty
Micro- and miniservices
A case study: Blogging and authentication
Get the Platinum pass or the Training pass to add this course to your package.
©2017, O'Reilly Media, Inc. • (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. • firstname.lastname@example.org