Journey of containerization on AWS

Journey of containerization on AWS

A lot of companies struggle with the challenge of transferring existing legacy applications into the cloud. Reasons for having such struggle: Complex business logic, software in a regulated environment, tightly integrated into to IT ecosystem, and much more.
This talk will show a possible way from having a legacy application running on-prem to a containerizes application running on AWS Fargate. By using as much as advantages of AWS managed services like CodePipeline with Codebuild, AWS Application Load Balancer, CloudWatch and more. But also by pointing at some trade-offs on this journey. To round this up, we will a brief look into the future for possible next steps.

953e885bfe36c3610179617201c22d6c?s=128

Nico Schilling

September 09, 2019
Tweet

Transcript

  1. 2.

    EUROPEAN LEADER IN PUBLIC CLOUD with local presence in 8

    countries. Nordcloud was born in the cloud 2011 and has grown to be the European leader in public cloud infrastructure solutions and cloud native application services. We are ranked globally #2 by Gartner capability assessment in Mode 2 use cases such as supporting agile applications and cloud native transformation. Our highly skilled organisation comprises of 300+ cloud experts with 180+ certifications and 200+ business and technical accreditations. About Nordcloud
  2. 3.

    OUR EXPERTISE IN MULTI-CLOUD HAS MADE US Strategic partner for

    AWS, Google and Microsoft. Partners with the leading technology companies from their respective fields.
  3. 4.

    OUR SERVICES About Nordcloud • Build a robust and future-proof

    foundation for your applications and servers. • Introducing maximum agility and flexibility for your business, creating the foundation for business innovation • Improve your processes and operations by moving IT to the public cloud. • Cut time to market to just minutes (compared to legacy months). • Boost your business and stay ahead of the competition with cloud native applications. • Benefit from scalability, as well as easier and more flexible management. • Benefit from new business insights through machine learning and artificial intelligence. • Improve decision making, adapt to changes quickly and open up new business opportunities.
  4. 5.

    Where we started from? • A legacy java application in

    customer branch offices • Complex network • A team with nearly no knowledge about Cloud and Container • No specification / no guidelines about the architecture
  5. 6.

    Where we started from? Branch office Client Local backend server

    Client Client Branch office • Application can’t be changed • Thousands of branches • Master data on local server
  6. 7.

    What do we want to achieve? • One API endpoint

    for all branches • Find a „good“ solutions in terms of architecture, price, operation • Ramp up the cloud / container knowledge inside the team • Iterate in an agile way
  7. 8.

    A journey of containerization on AWS Branch office Local backend

    server AWS Cloud Developer Public Subnet Private Subnet Amazon EC2 Elastic Load Balancing VPN Customer Network First shot
  8. 9.

    • Infrastructure as Code (CloudFormation) • Network separation • On-premise

    connection • Handling of the application • Provide a working environment First shot A journey of containerization on AWS • No scaling at all • Manual installation of application • Management overhead for EC2 • Only for one branch office • Suboptimal runtime environment • Expensive Achievements Trade off
  9. 11.

    Let‘s put it in a container! Putting the application in

    a container, helped us with the following: • A container can be scaled easier • The Dockerfile describes the installation of the container • No management overhead for the operating system • Very small management for Docker orchestration by using AWS ECS Fargate • Runtime environment way more suitable
  10. 12.

    Second shot with containers! Branch office Local backend server AWS

    Cloud Developer Public Subnet Private Subnet Elastic Load Balancing VPN Customer Network AWS Fargate
  11. 13.

    Second shot! What the team achieved? • Infrastructure as Code

    (CloudFormation) • Network separation • On-premise connection • The handling of the application • Provide a working environment • Installation is automated via Dockerfile • Scaling is easier • Eliminated OS management Trade-offs? • Docker deployment by hand • Docker container is very hardcoded
  12. 14.

    All good things come in threes! What we did in

    this stage? CI/CD for Docker: AWS Cloud Infrastructure Developer Public Subnet AWS Fargate AWS CodeCommit AWS CodePipeline AWS CodeBuild
  13. 15.

    All good things come in threes! What the team achieved?

    • Infrastructure as Code (CloudFormation) • Network separation • On-premise connection • The handling of the application • Provide a working environment • Installation is automated via Dockerfile • Scaling is easier • Eliminated OS management • Docker deployment by hand Trade-offs? • Docker container is very hardcoded
  14. 16.

    What could the future bring? In the future two huge

    points needs to be addressed: • Hardcoded Docker Image • Split Image into a base and branch image • Eliminate multiple processes in one Container • Support the operational processes more • Stream logs to Cloudwatch logs • Build CloudWatch Dashboards to support operation with more insides
  15. 17.

    Three stages until now A journey of containerization on AWS

    1 MVP Provide something that runs and can be used by the development team 2 Containerization Eliminate the most critical trade-offs from stage 1 3 Automation Let’s make it more comfortable for ourselves
  16. 18.

    Things for the next project: • Trade-offs are okay –

    as long as you have a clear pipeline to fix them • Be clear about your trade offs • One trade off should never exist: Security • Not starting with the whole Cloud World at ones, makes it a lot easier for newbies • Agility helps a lot finding a suitable solution • External consulting helps with guidance, upskilling and direction
  17. 19.

    THANK YOU! Let’s stay in touch LinkedIn: https://www.linkedin.com/in/nicoschilling/ Email: nico.schilling@nordcloud.com

    Image credits: • Photo by Danielle MacInnes on Unsplash • Photo by bruce mars on Unsplash • Photo by frank mckenna on Unsplash • Photo by Octavian Rosca on Unsplash • Photo by Joanna Kosinska on Unsplash