The CI/CD and DevOps Blog

Why the adoption of Kubernetes will explode in 2018

Kubernetes is an open-source orchestration engine for automating deployment, scaling, and management of containerized applications at scale. When your requires a large number of containers, you need a tool to group containers into logical units, and to track, manage and monitor them all.  Kubernetes helps you do that and is considered the de facto tool for container management.

The Kubernetes project is part of the Cloud Native Computing Foundation (CNCF) and has over 1500 contributors. It was started at Google, which still leads development efforts. 

Docker adoption is still growing exponentially and more and more companies have started using it in Production. It is important to use an orchestration platform to scale and manage your containers. Imagine a situation where you have been using Docker for a little while, and have deployed on a few different servers. Your application starts getting massive traffic, and you need to scale up fast, how will you go from 3 servers to 40 servers that you may require? And how will you decide which container should go where? How would you monitor all these containers and make sure they are restarted if they exit? This is where Kubernetes comes in. 

7 things to consider while moving to a microservices architecture

In part I of my four part blog series on Microservices, I explained what microservices are and the benefits you will see by adopting this architecture.

However, life is all about tradeoffs. In part II of this series, I will go over the things you need to consider while moving to microservices, as well as some challenges that crop up even when you do everything right.

Microservices for greenfield projects

Anytime your team develops a new application from scratch, it feels great not to inherit technical debt and be locked into outdated decisions made years ago.  Most teams developing new apps today would probably choose to containerize them using Docker and adopt microservices architecture for speed and agility.

What is Modern Application Delivery?

Development practices have come a long way since the time of Waterfall. Development shops have progressed through Agile methodologies and have built a culture of continuously delivering value to their customers, both internally and externally. Many shops have also since implemented Scrum and are experimenting with containerization technologies.

Top 5 Takeaways from Container Summit at Interop

Yesterday, I attended Container Summit: The Future of Containers in the Enterprise, which occurred in cooperation with the Interop conference.  Thanks to the great people at Joyent, it was a day packed with fantastic presentations and more than a few takeaways.  

My über takeaway from the day is that it's getting harder and harder to talk about containers without also talking about microservices. There were examples of containers in use for a variety of use cases, but it was their particular suitability for use with microservices that came through loud and clear.

In addition to that uber takeaway, here were my top five takeaways from the summit:

  1. Microservices are the next big tech wave
  2. Microservices create complexity
  3. Developer experience and developer velocity are key success factors
  4. There likely won't be one winner for container orchestration
  5. Running containers on bare metal isn't just for the brave

And check below for my favorite one-liner from the event :)

While Containers Move to the Mainstream, Some Roadblocks Exist on Path to Adoption

Developers are increasing their use of containers for new applications, but a technology skills gap is impeding widespread adoption of container technology. These are two of the key findings of our latest survey on container adoption among developers. Shippable worked with independent research firm Survata to survey of 300 developers about their current and expected use of container technologies. The results were interesting in a number of ways.