A server-less CI/CD approach for mono-repo micro-frontends

1

AWS Lambda

The API Gateway triggers an AWS Lambda function which authenticates the request, analyses the event and, based on affected files, triggers a pipeline for the micro-frontend where the files belong to.

#Cloud Computing #Cloud Hosting #Backend As A Service 248 social mentions

2

AWS CodePipeline

#Continuous Integration #DevOps Tools #Continuous Deployment 28 social mentions

3

AWS CodeDeploy

#DevOps Tools #Continuous Integration #Continuous Deployment 13 social mentions

4

AWS CodeBuild

#Continuous Integration #DevOps Tools #Continuous Deployment 13 social mentions

5

Amazon CloudWatch

The integration is ready! Pushing a file to the repository will result in a “Hello world” message triggered by the Lambda, which can be seen under its stream logs in Cloudwatch. Let’s now update Lambda code to make sure that we support CI/CD for any micro-frontends in your repo.

#Monitoring Tools #Log Management #Application Performance Monitoring 54 social mentions

6

Amazon CloudFront

Changes are available in S3 bucket and exposed on a Cloudfront distribution.

#CDN #Cloud Computing #Content Distribution 67 social mentions

7

Amazon API Gateway

Developers push their code to the main branch in GitHub, which will trigger a push event via GitHub webhooks to an AWS API Gateway responsible to handle the event.

#API Tools #APIs #Web Service Automation 95 social mentions