Microservices
Richard Li
Modern applications are systems, not just code. These applications are built from many different parts. For example, a modern application might consist of a handful of microservices (containing business logic) that use ElasticSearch (for search), Redis (for caching), and a PostgreSQL instance (for data storage).
In this applications-are-systems world, existing deployment systems start to show their age. A previously simple task such as installing your application for local development now becomes a long Wiki document with dozens of steps to setup and configure dozens of different components.
March 27, 2018 | 9 min read
Kubernetes
We have multiple clusters and namespaces: some for production, some for load testing, and some for development. In the course of our day-to-day development, we’ve found a number of useful tools that improve our productivity.
(ProTip: A productivity killer is typing kubectl delete ns foo … in the wrong cluster. The first two tools below help address that problem.)
kubectx/kubens, which lets you easily switch between clusters and namespaces.
March 12, 2018 | 1 min read
Microservices
In a microservice architecture, services communicate with each other through L7 protocols such as gRPC and HTTP. Since the network is not reliable (and services can go down!), managing L7 communications is critical for reliability and scale.
February 28, 2018 | 4 min read
Kubernetes API Gateway
This article was updated in December 2021.
This article will introduce the three general strategies in Kubernetes for ingress, and the tradeoffs with each approach. I’ll then explore some of the more sophisticated requirements of an ingress strategy. Finally, I’ll give some guidelines on how to pick your Kubernetes ingress strategy.
What is Kubernetes ingress?
February 28, 2018 | 12 min read
API Gateway
What is Canary Deployment?
Canary deployments are a popular technique for incrementally testing changes on real-world traffic. In a traditional application, canary deployments occur on the granularity of the entire application. This limits the utility of canary deployments, as a single feature cannot be tested against real-world traffic.
With a microservices architecture, this is no longer the case. A single service team is able to test their updates with real-world users.
February 22, 2018 | 5 min read
Telepresence
A guide to setting up shared development environments for teams on Kubernetes.
Is Minikube melting your laptop? Are your local integration tests suffering because you can’t run dependencies on your development machine?
As organizations adopt Kubernetes and cloud native architectures, development teams will often run into resource constraints as their architectures get more complex. Additionally, Kubernetes presents new challenges for configuring local development environments in comparison with legacy monolithic applications.
January 18, 2018 | 5 min read
