The CI/CD and DevOps Blog

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.

undefined-864167-edited.jpg

Deploying Containers to Elastic Beanstalk, the Shippable way!  

 

 

Warning-Icon.png

DEPRECATED BLOG:

We have significantly updated the Shippable platform with several new features. Hence most of the content in this blog is deprecated. For the latest information, refer to our documentation and/or open a support issue, if you have questions.

You can also refer to our new blog on this topic: How To: Deploy your application to AWS Elastic Beanstalk (Part 1)


 

 

Last month we introduced the ability to deploy Docker containers to Amazon AWS Elastic Beanstalk (EBS) as the last step in a Shippable CI/CD pipeline.  In this article, I will walk through the steps required to set this up in Shippable and execute a deployment to EBS.

AWS Elastic Beanstalk is an easy-to-use service for deploying and scaling web applications and services developed with Java, .NET, PHP, Node.js, Python, Ruby, Go, and Docker on familiar servers such as Apache, Nginx, Passenger, and IIS.