Article
Tutorial: Learn to locally debug Spring Boot microservices with IntelliJ and Telepresence connected to a remote Kubernetes cluster
Many Java- and Spring-based organizations adopt cloud native development practices with the goal of shipping features faster. The technologies and architectures may change when we move to the cloud -- just look at the rise of Spring Boot, Spring Cloud and microservices -- but the fact remains that we all still add the occasional bug to our code. The challenge here is that many of your existing local debugging tools and practices can’t be used when everything is running in a container or on the cloud. Embracing new tooling is required!
Local Debugging with Mocks and Stubs Only Gets You So Far
March 25, 2019 | 14 min read
Kubernetes
How to set up a local Kubernetes cluster on Windows to test applications easily
Containerized applications offer many advantages over traditional deployments, from ease of management to scalability and isolation. Hence, combining containerized applications with a proper orchestration engine is the best way to manage modern applications in both staging and production environments.
As Windows Developers, we need a proper Kubernetes environment to test our applications. This article focuses on setting up a local Kubernetes cluster that enables us to test our applications easily. To do this, we will cover:
March 18, 2019 | 9 min read
Platform Engineering
DevOps, GitOps, and the Rise of Cloud-Native Engineering
February 14, 2019 | 8 min read
Article
Organizations are increasingly deploying multiple Kubernetes clusters to improve availability, isolation and scalability. Learn about the benefits of building multi-cluster Kubernetes applications, how to architect them, and the strategies available for implementing them.
What is Multi-Cluster?
Multi-cluster is a strategy for deploying an application on or across multiple Kubernetes clusters with the goal of improving availability, isolation, and scalability.
September 25, 2018 | 5 min read
API Gateway
People ask a common question “should I use Edge Stack API Gateway if I’m using a service mesh (usually Istio)?” After all, both Ambassador and Istio are built on the Envoy Proxy. Moreover, Istio recently added support for explicitly managing ingress with the Gateway abstraction. So, do you need an API Gateway if you’re using a service mesh?
Ambassador (and API Gateways in general) focus on north/south traffic, i.e., traffic into your data center. Istio (and other service meshes) handle east/west traffic, i.e., traffic between services in your data center. If your service mesh already manages L7 traffic, can you use it for managing north/south traffic?
TL; DR
September 14, 2018 | 5 min read
API Gateway
Description
Onefootball is a media company with more than 10M monthly active users delivering more than 10 TB daily content. We needed a Kubernetes-based API Gateway and Ingress solution that could handle our 6,000 rps workload reliably and efficiently. In this session, we'll talk about why we chose the open source Edge Stack Kubernetes API gateway, and how we made the migration to it. We will cover the challenges identified and the benefits we've seen, like:
Cost reduction: Reduced the number of cloud-based load balancers from ~100 to 4.
September 6, 2018 | 27 min read