Advanced Microservices

Transcription

1 Advanced Microservices A Hands-on Approach to Microservice Infrastructure and Tooling Thomas Hunter II

2 Advanced Microservices: A Hands-on Approach to Microservice Infrastructure and Tooling Thomas Hunter II San Francisco, California, USA IISBN-13 (pbk): ISBN-13 (electronic): DOI / Library of Congress Control Number: Copyright 2017 by Thomas Hunter II This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Trademarked names, logos, and images may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, logo, or image we use the names, logos, and images only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. While the advice and information in this book are believed to be true and accurate at the date of publication, neither the authors nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may be made. The publisher makes no warranty, express or implied, with respect to the material contained herein. Managing Director: Welmoed Spahr Editorial Director: Todd Green Acquisitions Editor: Louise Corrigan Development Editor: James Markham Technical Reviewers: Anthony Leontiev, Jonathan Kuperman, and John Sheehan Coordinating Editor: Nancy Chen Copy Editor: Kim Wimpsett Distributed to the book trade worldwide by Springer Science+Business Media New York, 233 Spring Street, 6th Floor, New York, NY Phone SPRINGER, fax (201) , orders-ny@springer-sbm.com, or visit Apress Media, LLC is a California LLC and the sole member (owner) is Springer Science + Business Media Finance Inc (SSBM Finance Inc). SSBM Finance Inc is a Delaware corporation. For information on translations, please rights@apress.com, or visit rights-permissions. Apress titles may be purchased in bulk for academic, corporate, or promotional use. ebook versions and licenses are also available for most titles. For more information, reference our Print and ebook Bulk Sales web page at Any source code or other supplementary material referenced by the author in this book is available to readers on GitHub via the book s product page, located at For more detailed information, please visit Printed on acid-free paper

3 Contents at a Glance About the Author... xiii About the Technical Reviewers... xv Preface... xvii Chapter 1: Introduction... 1 Chapter 2: HTTP API Design Chapter 3: Deployments Chapter 4: Service Discovery Chapter 5: Service State Chapter 6: Consumers Chapter 7: Monitoring Chapter 8: Documentation Chapter 9: Collaboration References Index iii

4 Contents About the Author... xiii About the Technical Reviewers... xv Preface... xvii Chapter 1: Introduction... 1 Why Use Microservices?... 1 Forced Separation of Concerns...1 Natural Team Ownership...1 Frequent Deployments...2 Heterogeneous Selection of Languages... 2 Organization Buy-In... 2 Separation of Concerns... 3 Nouns (Entities)...3 Verbs (Actions/Relationships)...3 Example Microservice Breakdown...4 Team Structure...5 Splitting a Monolith... 6 Terminology... 7 Networking Basics... 8 Hostnames and IP Addresses...8 Network Interfaces...9 Ports...10 Protocols...11 v

5 Contents Chapter 2: HTTP API Design Data Design and Abstraction Examples of Abstraction...14 Real-World Examples...16 Anatomy of an HTTP Message Debugging HTTP Traffic...18 API Entrypoint Choosing an Entrypoint for a Public API...19 Content Located at the Root...20 API Requests HTTP Methods...21 URL Endpoints...23 Filtering Resources...25 White-Listing Attributes...26 Requesting Arrays via URL Parameters...27 Body Formats...28 HTTP Headers...30 API Responses HTTP Status Codes...31 Content Types...33 Expected Body Content...34 JSON Attribute Conventions...36 Error Reporting...40 Responses Should Mimic Requests...43 HTTP Headers...44 API Standards Simple Response Envelope...45 JSON Schema...46 vi

6 Contents JSON API...46 GraphQL...47 Hypermedia APIs...49 API Transports JSON RPC...51 SOAP...52 MessagePack (Binary)...53 Apache Thrift (Binary)...54 Chapter 3: Deployments Automated Testing Unit Tests...55 Smoke Tests...56 Integration Tests...56 Acceptance Tests...56 Performance Tests...56 Regression Tests...56 Containers Docker Containers...58 Managing Containers with Kubernetes...62 Further Reading: Mesos and Marathon...63 Build Pipeline Continuous Integration and Deployment...64 Choosing Environments...64 Designing a Build Pipeline...65 Building with Jenkins...67 Testing Contributions...70 Further Reading: TeamCity and CircleCI...72 vii

7 Contents Chapter 4: Service Discovery Why Do You Need Service Discovery? Client Side vs. Server Side Client-Side Discovery...75 Server-Side Discovery...75 Example Implementation Get Entire State...76 Register Provider Instance...77 Deregister Provider Instance...77 Finding a Provider...78 Periodic Health Checks in Provider...79 Application Discovery with Consul Registering a Service Instance...80 Passing a Health Check...81 Deregistering a Service Instance...81 Subscribing to Updates...81 HTTP Routing with Consul Limitations of Common Web Servers Consul, Consul Template, HAProxy...84 Further Reading Apache ZooKeeper and Apache Curator Netflix Eureka...86 Etcd...87 Elastic Load Balancer (ELB)...87 Chapter 5: Service State Relational Storage with PostgreSQL RETURNING Clause...94 When to Use PostgreSQL...94 viii

8 Contents When Not to Use PostgreSQL...94 Further Reading: MySQL...95 Document Storage with MongoDB When to Use MongoDB When Not to Use MongoDB Further Reading: CouchDB Fast Data Structures with Redis Data Types Atomic Operations with MULTI/EXEC Execute Lua Scripts on Redis Server Caching Pub/Sub with PUBLISH/SUBSCRIBE When to Use Redis When Not to Use Redis Further Reading: Memcached Document Search with Elasticsearch Populating Elasticsearch Chapter 6: Consumers User Agents API Versioning Versioning via URL Segment Versioning via the Accept Header Versioning via a Custom Header API Deprecation Authentication and Authorization Two-Legged Authentication (2LA) Three-Legged Authentication (3LA) Real-World Usage ix

9 Contents x Consumer Permissions Per-Authorization Permissions Default Consumer Permissions Rate Limiting Chapter 7: Monitoring Logging ELK: Elasticsearch, Logstash, Kibana Transmitting Logs via Logstash Querying Logs via Kibana Request UUID Tracking Dynamic Log Verbosity Analytics Grafana, Graphite, and StatsD Transmitting Data via StatsD Querying Data via Grafana Tracking Overall Incoming Requests Tracking Outbound Requests Track Everything Alerting When Not to Alert Error Thresholds Having Someone Else Respond External Tools (Software as a Service) Internal Tools (Self-Hosted) Chapter 8: Documentation Good Documentation Principles Convenience of Developer Testing Web-Based Developer Console Providing curl Commands...152

10 Contents Discovering Documentation Documentation Generators Swagger Chapter 9: Collaboration The Importance of Collaboration Common Debugging Tools curl and jq Postman Paw (Mac Shops) Fiddler 2 (Windows Shops) Shared Modules Minimize Languages and Frameworks Be Precise When Reporting Bugs Example of a Poorly Described Bug Example of a Nicely Described Bug Generate curls Programmatically Patches Welcome References Index xi

11 About the Author Thomas Hunter II is a principal software engineer at OpenTable where he maintains microservices, builds new ones as needed, and generates curl requests for other teams to debug their services. His nights are occasionally spent giving talks at meetups and conferences. Thomas previously worked as an API architect for Barracuda Networks Copy.com, a filesharing and storage service, where his main concern was getting a nicely documented API into the hands of third-party developers. xiii

12 About the Technical Reviewers Anthony Leontiev is a senior architect at AltSchool, where he is a team lead on front and back-end development projects. He was previously a software engineer at Honest Buildings and has worn various hats at early to mid-stage startups. Anthony is building Asaak s mobile platform and automating the loan origination process. He is experienced with Python, Django, Ember, JavaScript, and React Native. Jonathan Kuperman is a software engineer who is passionate about JavaScript, web performance, and accessibility. Jon worked as an engineer at Brave where he built a faster, safer, open source browser with Node.js and JavaScript. Before that he worked as a software engineer at Twitter, making the home timeline fast and accessible. He spends his free time speaking at conferences and giving workshops. He creates educational videos at Nodecasts.io for new developers. He is also the host of The Web Behind podcast, interviewing well-known developers on how they got their start in technology. John Sheehan is an API fanatic with more than 15 years of experience working in a wide variety of IT and software development roles. As an early employee at Twilio, John led the developer evangelism program and worked as a product manager for Developer Experience. After Twilio, John was the platform lead at IFTTT working with API providers to create new channels. John is also the creator of Rest Sharp, API Digest, and API Jobs and is the cohost of Trac and Weather, an API and cloud podcast. xv

13 Preface This book covers a breadth of knowledge for adopting and implementing redundant and highly available microservices within an organization. Preference is given to a stack built upon open source technologies. I use as few application code examples as possible to make this book language-agnostic. I also cover example network payloads and configuration files where applicable. I explain some basic concepts such as how to design your application programming interface (API), how to keep track of other services consuming your API, and how to document your API. I cover how to deploy your API and let others know where your API can be found. I also explain how to keep your API alive and healthy using analytics, monitoring, and logging, and even have it alert you if it isn t healthy. I even discuss tools and methods for collaborating with other teams to keep the organization happy. Intended Audience Whether you already work for an organization that practices microservices or would like to convince your organization to start doing so, this book is for you. If the prior, it is my hope that this book will bring some understanding to your chaotic workday. If the latter, it is my hope to bring chaos to your orderly workday. The ideal reader of this book is someone who has built several web sites and is comfortable working with a web language or framework, as well as having some intermediate knowledge such as how to read and write HTTP headers. Comfort with version control, especially with Git, is also beneficial. Tools Here are some tools that will help you not only while reading this book but also throughout your career as a microservice developer. I will cover them repeatedly throughout this book, so please install them. curl (curl.haxx.se): Command-line Hypertext Transfer Protocol (HTTP) client jq (stedolan.github.io/jq): Command-line JavaScript Object Notation (JSON) transformer Postman (getpostman.com): Graphical HTTP client xvii

14 Preface Once you have curl and jq installed, you will be able to run commands like this: $ curl jq \ "{name:.name, home:.location, where_to_spam:. }" { "name": "Thomas Hunter II", "home": "San Francisco, CA", "where_to_spam": "me@thomashunter.name" } xviii