Containers are increasingly becoming the de-facto strategy for cloud native deployments. With the question of orchestration looming over those deployments, cloud vendors continue to provide multiple offerings for managing your containerized services. In this article, we’ll compare 3 main Azure offerings for container orchestration: Azure Web Apps, Azure Container Instances, and Azure Kubernetes Service.
Organizations across all industries are reaping the benefits of powering their business solutions in the cloud. However, selecting a provider for your cloud-native applications can be a tough decision. There are many options to choose from that have a variety of managed services to help you successfully transition to a cloud-native architecture. In this article, we explore three reasons why Microsoft Azure is one of the most popular options for hosting your application in the cloud.
The principle “build once, deploy anywhere” is a fundamental part of Continuous Delivery and Deployment. If your underlying architecture is not built to support this behavior, you’re creating quite a few headaches for yourself and your Continuous Integration/Continuous Delivery/Deployment (CI/CD) pipeline. By following a few guidelines, you can ensure that the Artifact (the built code) you create is the same throughout each environment. In this article, we walk through a CI/CD pipeline deploying to AWS Elastic Container Service for Kubernetes (EKS) that simplifies the deployment process and guarantees the “build once, deploy anywhere” principle is followed.
Technology is ever-changing, and the options available to product teams continue to expand. Coordinating a team around a technology stack can be challenging, but it’s a necessary practice to enable faster delivery.
In this article, we’ll show you how we worked with one product delivery team to realize the benefits of adopting .Net Core and developed a template application that could be used for future development efforts.
Going cloud-native and choosing AWS as your cloud platform is an important decision. Once you’ve set your mind to that path, the next step is to select the right managed services for your infrastructure. If you’re implementing a microservice approach on AWS, there are multiple options for hosting your containerized services. Here is a high-level overview of ECS, Fargate, and EKS and tips for choosing the best container orchestration option for your organization.