These days, you can’t swing a dry-erase marker without hitting someone talking about microservices. Developers are studying Eric Evans’s prescient book Domain-Driven Design. Teams are refactoring monolithic apps, looking for bounded contexts, and defining a ubiquitous language. And while there have been countless articles, videos, and talks to help you convert to microservices, few have spent any appreciable time asking if a given application should be a microservice. Nathaniel Schutta shows you a set of factors you can apply to help you decide if something deserves to be a microservice or not. You’ll also look at what you need to do to maintain a healthy micro(services)biome.
Nathaniel T. Schutta is a software architect focused on cloud computing and building usable applications. In addition to his day job, he’s an adjunct professor at the University of Minnesota, where he teaches students to embrace dynamic languages. A proponent of polyglot programming, Nate has written multiple books, including Presentation Patterns, with Neal Ford and Matthew McCullough, written to rid the world of bad presentations. He’s also appeared in various videos and is a seasoned speaker, regularly presenting at conferences worldwide, No Fluff Just Stuff symposia, meetups, universities, and user groups.
Comments on this page are now closed.
©2019, 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