Thanks to everyone who reached out following last week’s inaugural IT Modernization Week in Review blog. Containers and container orchestration were in the news this week and that should come as little surprise as container adoption continues to grow. In fact, Gartner predicts that by 2020, more than 50% of global organizations will be running containerized applications in production, up from less than 20% today.
In few industries is innovation more important than in the rapidly changing, highly competitive retail market. Tasked with servicing the organization’s eCommerce site and in-store systems, today’s AWS case study is about a well-known household name retailer who approached the DevOps team at Flux7 about enabling their in-house development team to stay nimble and one step ahead of the competition.
As an AWS Premier Consulting Partner, we are often asked about using the Kubernetes container management system within AWS. While Google created Kubernetes (K8s), Google’s Cloud Platform is generally seen as a better fit for running K8s clusters. However, until the recent re:Invent announcement of EKS, KOPS, the Kubernetes project for managing production-grade K8s clusters, was the best tool to deploy and manage K8s clusters in AWS. Which brings us to the topic of today’s blog, a customer story of how we used KOPS to run AWS-based K8s clusters. Stay tuned for the second part of today’s AWS case study in which we discuss the details of doing so with Ubuntu CIS benchmark images.
At Flux7, we are passionate about sharing the power of DevOps. In that vein, we recently gave a workshop introducing developers to the power, ease of use, and governance that comes with moving to a DevOps model reinforced with well-architected tooling. The goal of the workshop was to teach developers more about AWS and Docker-based microservices architecture. And, how using Amazon services like EC2 Container Service, CodePipeline, and CodeBuild can come together to create a platform for developer teams to focus on their application. We highlighted the Anchore solution as part of our microservices architecture for security and will share in today’s blog why we deployed Anchore, how we used it to ensure DevOps security and policy compliance, and our overall experience with the tool.
Join us Thursday, August 24th in Austin, TX for a dynamic one-day microservices architecture and Amazon ECS workshop session.
In 2013 Gene Kim, Kevin Behr and George Spafford published The Phoenix Project, a book that marries the concepts of manufacturing agility from Eliyahu Goldratt’s The Goal and relates them to IT. As they elucidate in the story, a new approach to IT is clearly needed and many organizations are embracing that change through the DevOps methodology. However, DevOps can be a very broad term making it difficult for people to know where to begin. As a result, we have narrowed the DevOps model
At the recent Austin DevOps Days Conference, Flux7 CEO Aater Suleman gave a talk on the "Top Ten Considerations When Planning Docker-based Microservices”. For those of you unable to attend the conference, you can listen to a replay of the presentation here. Or, read on as we share part of his talk focused on the synergy between DevOps, Docker and building microservices.
Docker is becoming a cornerstone of DevOps architectures with its lightweight, portable, “build once, configure once, and run anywhere” containers. And, for all those who would like to get a jumpstart on building their Docker skills, Flux7 CTO Ali Hussain will be presenting a half-day tutorial workshop on Docker fundamentals on Tuesday, June 6th at the DevOps West Conference.
Flux7 CEO Aater Suleman will be speaking at DevOps Days Austin 2017, taking place May 4-5, 2017 Aater’s talk, titled "Top Ten Considerations When Planning Docker-based Microservices” is on Friday May 5th, starting at 4:50 pm. See the full program here.
Microservices are being adopted widely across organizations of all sizes and all industries for their ability to increase service delivery and speed time to market while decreasing team overhead. Replacing monolithic apps -- or building greenfield ones -- with microservices makes some applications easier to build and maintain, making it easier to deliver technology quickly in today’s competitive landscapes.
Docker containers are a natural fit for microservices as they inherently features autonomy, automation, and portability. Docker is known for its ability to encapsulate a particular application component and all its dependencies thus enabling teams to work independently without requiring underlying infrastructure or the underlying substrate to support every single one of the components they are using. In addition, Docker makes it easy to create lightweight, isolated containers that can work with each other while being very portable.
However, before jumping head first into a container-based microservice strategy, careful planning and implementation is needed. Doing so will help avoid costly rework and other headaches down the road.
Based on proven success using Docker, Flux7’s Aater Suleman shares essential tips and requirements for building, deploying and operating successful microservices on Docker-ized infrastructure.
If you're attending DevOps Days Austin, please join Aater for his talk or drop us a line to say hello. And, if your organization is interested in learning more about microservices and container strategy, please access our articles on the topic here, or subscribe to our blog below for ongoing analysis, case studies, and tips & tricks.
Join Flux7’s Aater Suleman at DevOp Days Austin
Friday, May 5 • 4:50pm - 5:25pm, Centennial Room Right
Top Ten Considerations When Planning Docker-based Microservices
- Watch Aater and Cars.com co-present at DockerCon
- Watch Aater and Fugro co-present at DockerCon
- Watch “Container Based Migrations” from AWS re:Invent