GitXplorerGitXplorer
a

aws-serverless-ecommerce-platform

public
1119 stars
382 forks
33 issues

Commits

List of commits on branch main.
Verified
3b9ef36dd3e338c8ab697c2bcb1b672e064e303c

Merge pull request #201 from aws-samples/dependabot/npm_and_yarn/payment-3p/minimist-1.2.6

nnmoutschen committed 3 years ago
Verified
4798ceb72dbf93ee6bb7c786c6e9f53d2db5d524

chore(deps): bump minimist from 1.2.5 to 1.2.6 in /payment-3p

ddependabot[bot] committed 3 years ago
Verified
efee84c85f2bcde05e81e4f3fdda8f3f6b8c6522

Merge pull request #198 from aws-samples/dependabot/npm_and_yarn/payment-3p/vm2-3.9.7

nnmoutschen committed 3 years ago
Verified
68a2067ce114d2aa4fb333d9840108cc6813427f

chore(deps): bump vm2 from 3.9.5 to 3.9.7 in /payment-3p

ddependabot[bot] committed 3 years ago
Verified
ce30291be1df0dca6f33c1eb4e3c55b668549807

Merge pull request #197 from aws-samples/dependabot/npm_and_yarn/payment-3p/follow-redirects-1.14.8

nnmoutschen committed 3 years ago
Verified
24eead0c4206d38b54abeed88b78d434fdb74a57

chore(deps): bump follow-redirects from 1.14.7 to 1.14.8 in /payment-3p

ddependabot[bot] committed 3 years ago

README

The README file for this repository.

AWS Serverless Ecommerce Platform

Status: Work-in-progress. Please create issues or pull requests if you have ideas for improvement.

The Serverless Ecommerce Platform is a sample implementation of a serverless backend for an e-commerce website. Functionalities are split across multiple micro-services that communicate either through asynchronous messages over Amazon EventBridge or over synchronous APIs.

This sample is not meant to be used as an e-commerce platform as-is, but as an inspiration on how to build event-driven serverless microservices on AWS. This makes lots of assumptions on the order flow that might not be suitable for most e-commerce platform and doesn't include many of the features that you might need for this.

Please note that you may incure AWS charges for deploying the ecommerce platform into your AWS account as not all services used are part of the free tier and you might exceed the free tier usage limit. To track costs in your AWS account, consider using AWS Cost Explorer and AWS Billing and Cost Management. You can also set up a billing alarm to get notified of unexpected charges.

High-level flow across microservices

Getting started

To install the necessary tools and deploy this in your own AWS account, see the getting started guide in the documentation section.

Architecture

High-level architecture

This is a high-level view of how the different microservices interact with each other. Each service folder contains anarchitecture diagram with more details for that specific service.

High-level architecture diagram

Technologies used

Communication/Messaging:

  • AWS AppSync for interactions between users and the ecommerce platform.
  • Amazon API Gateway for service-to-service synchronous communication (request/response).
  • Amazon EventBridge for service-to-service asynchronous communication (emitting and reacting to events).

Authentication/Authorization:

  • Amazon Cognito for managing and authenticating users, and providing JSON web tokens used by services.
  • AWS Identity and Access Management for service-to-service authorization, either between microservices (e.g. authorize to call an Amazon API Gateway REST endpoint), or within a microservice (e.g. granting a Lambda function the permission to read from a DynamoDB table).

Compute:

  • AWS Lambda as serverless compute either behind APIs or to react to asynchronous events.

Storage:

  • Amazon DynamoDB as a scalable NoSQL database for persisting informations.

CI/CD:

Monitoring:

Backend services

Services Description
users Provides user management, authentication and authorization.
products Source of truth for products information.
orders Manages order creation and status.
warehouse Manages inventory and packaging orders.
delivery Manages shipping and tracking packages.
delivery-pricing Pricing calculator for deliveries.
payment Manages payment collection and refunds.
payment-3p Simulates a third party payment system.

Frontend service

Services Description
frontend-api User-facing API for interacting with the services.

Infrastructure services

Services Description
pipeline CI/CD pipeline for deploying the resources in production.
platform Core platform resources for deploying backend services.

Shared resources

Name Description
docs Documentation application for all services.
shared Shared resources accessible for all services, such as common CloudFormation templates and OpenAPI schemas.
tools Tools used to build services.

Documentation

See the docs folder for the documentation.

Contributing

See the contributing and getting started documents to learn how to contribute to this project.

License

This library is licensed under the MIT-0 License. See the LICENSE file.