We’re familiar with huge software applications that are built from many tightly related parts. After all, that’s how things grow: you start with a simple web site, then add login and authentication, then add some e-commerce, start taking credit cards, integrate with other services, add recommendations, and pretty soon you have a giant mass of code. We’ve gotten reasonably good at making these applications work, but there’s a better way. Applications can be now broken into microservices: specific services that solve one very specific part of the overall problem, communicating via the network. But how do we know if microservices are a good fit for our system architecture? What are some common microservice patterns, antipatterns and pitfalls? What concerns do we need to keep in mind once we’ve made this transition?
©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