Skip to content

rodrigopasc/ZaptalkNotificationMicroservice

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ZapTalk Notification Microservice

Microservices

Fake notification microservice example.

This event-driven microservice is just a mock that represents a notification sender. ✉️

Architecture Design

Briefing

Assuming the goal is to build a highly scalable, robust, reliable checkout service that meets the standards of AWS Well-Architected, this project takes the most of the serverless design pattern and communicate with other microservices through Amazon SNS.

Architecture

  • Checkout Microservice
    • It starts the checkout process by doing what the application needs and then communicate via SNS to the invoice microservice.
  • Invoice Microservice
    • Generate its invoice file, uploads to S3 and communicate via SNS to both logger and notification microservices.
  • Logger Microservice
    • Receive the information, customer details, generated invoice S3 URL and then persists on DynamoDB.
  • Notification Microservice
    • When the invoice microservice informs that the invoice itself was successfully generated, then this microservice sends the notification to the customer.

Dependencies

Setup

  • Copy secrets.json.example, update with your information and rename it to secrets.json.
  • Run $ serverless config credentials -o --provider aws --key=YOUR_AWS_KEY --secret YOUR_AWS_SECRET.
  • Deploy to AWS $ serverless deploy.

Releases

No releases published

Packages

No packages published