The latest posts and insights about Ambassador Labs - our products, our ecosystem, as well as voices from across our community.
Kubernetes API Gateway
Migration from Monolith to Microservices Many engineering teams are transitioning from monoliths to microservices. While this migration pattern has become common, certain important aspects are often overlooked. One such critical component is the role of an edge or API gateway, which plays a vital part in the transition. Common Focus Areas in Migration
Kubernetes API Gateway
EKS clusterAWS (Amazon Web Services) is a cloud platform offering over 200 products across various technologies. Among them is Amazon Elastic Kubernetes Service (EKS), a tool for orchestrating containers. Kubernetes is a platform for managing and deploying containerized applications. It is often used with container engines like Docker, CRI-O, and Containerd to enhance control over application deployment. In this article, you’ll explore the Amazon EKS architecture and learn two ways to deploy a Kubernetes cluster on AWS — through the AWS console and from your local machine.
API Development
Much like the rainbow road level in the popular Mario Kart games, the API development world is getting more and more complex. How do you power up your dev team to complete each level faster and better? Let’s get into the top five “cheat codes” that will put your dev team in the winner’s circle. From design through testing, this blog will share how to give developers ultimate control over the development process, pursue spec-first development, and remove infrastructure obstacles from impeding the advancement of your API strategy. If you’re more of a listener than a reader, you can watch my 2024 API world talk on the same topic below.
Kubernetes API Gateway
What is gRPC? gRPC is an RPC protocol built on HTTP/2 (gRPC Remote Procedure Calls) and is an open-source, high-performance framework developed by Google that allows communication between applications or services. It's particularly popular for microservices and distributed systems because of its efficiency, scalability, and support for multiple languages. We’re seeing more and more companies move their APIs from HTTP/JSON to gRPC. gRPC offers several benefits over HTTP/JSON: Performance. gRPC uses HTTP/2, with support for streaming, multiplexing, and more (see the difference in action). In addition, gRPC has native support for protobuf, which is much faster at serialization/deserialization than JSON.
API Development
With more and more people using web and mobile applications for everyday activities such as shopping, listening to music, and watching movies, applications nowadays must handle a tremendous workload. To ensure that your application can handle an expected user load, load testing must be executed before releasing the application. However, implementing and debugging your load tests can be tricky. With many simulated requests, it could be daunting to find the root cause of your performance issues by scrolling into pages of the log files. Well, executing the load testing for your application does not need to be like that. This article will teach you how to implement and debug a load test for a Go application running inside a Kubernetes cluster using k6 and Telepresence. Prerequisites
Telepresence
Adopting a microservice architecture is a great way to improve scalability and resilience in software systems, but it introduces new challenges, one of which is managing technical debt. When we talk about tech debt, we’re referring to the imperfections and shortcuts developers use in their code base, which becomes bad code over time. When these imperfections are left unaddressed, they can lead to longer development cycles, increased maintenance costs, bugs, etc. Technical debt has plagued the software industry since the early days and continues to do so today. This article explains technical debt, how it occurs, and how to manage tech debt in a microservice architecture.
