Home 5G Edge DevOps Transformation via CI/CD on AWS

Edge DevOps Transformation via CI/CD on AWS

by Vamsi Chemitiganti

Enterprise edge and IoT architects considering the K8s ecosystem for tools and architecture quickly recognize that the widest possible choices to develop microservices-based applications that fit well into a CI/CD model are available in the community.  This blog post considers the key requirements for CI/CD methodologies from an edge standpoint whether it’s a thick or a thin edge. 

Key requirements include,

  1. Given the scale of most enterprise applications, multiple teams need to work on a given codebase with centralized release management. Different teams work on the user interface, the domain model, business functionality, etc. The methodology needs to support multi-tenancy from a development team standpoint
  2. Need to support polyglot language and database development
  3. Need to support Independent load & performance testing
  4. Support application versioning and rollback 
  5. Support traffic shaping and independent updates for edge applications

While I have added detailed descriptions in the diagram above, we leverage the following AWS services to construct the pipeline:

The next post will discuss why there is no one definition of Edge and the various kinds of ‘Edges’ to expect in the years to come – whether it’s 5G/Travel & Hospitality, Manufacturing or Retail etc.

Discover more at Industry Talks Tech: your one-stop shop for upskilling in different industry segments!

You may also like

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.