In a previous story, the Payments team managed to deliver a multi-tenant functionality based on GraphQL and DynamoDB. It is now the time for the Accounts team to shine! They will expose a RESTful Accounts API via API Gateway, an AWS managed service responsible to manage APIs. The actual business logic will be implemented via a Lambda function which will retrieve data from an Aurora RDS cluster based on Postgres database. This is how our Accounts module architecture will look like at the end of this story.
After establishing a micro-frontend architecture and its deployment via Amplify in two previously published stories, it’s now time to focus on the Amplify supported backend capabilities. We will setup a simple multi-tenant application with a payments service based on AWS AppSync, a managed GraphQL API. Whole code can be found on Github.
Scope of this story is to:
User interface will differ a…
In a previous story, we created a simple web application leveraging a micro-frontend architecture. Now it is time to deploy our app to the cloud. This story - Part 2 - is going to be “AWS-heavy”, as we deep dive into various AWS resources and services. The end result will be the deployment of the web app to AWS, which you can access from your machine.
We want to design and deploy below architecture by focusing on two areas:
Excited? I am!
This story is the first part of a series of tutorials where, starting from a trivial micro-frontend (MFE) application, I will dive deep in AWS Amplify, a very promising framework allowing developers (and I would say start-ups) to easily build and deploy full-stack applications managed by AWS.
This mini-series will consists of different parts:
Tech Lead with a passion for frontend, backend and cloud