A basic example of a microservice architecture.
To run the example locally, clone the Github repository and start the services using Docker Compose. Once Docker finishes downloading and building the images, the front end is accessible by visiting
git clone https://github.com/ebosas/microservices cd microservices
deployments directory, create the pipeline stack. It will provision all the resources (network, cluster, etc.) and create a pipeline for each service. At this point, we have yet to build our service images.
aws cloudformation deploy \ --stack-name Microservices \ --template-file pipeline.yml \ --parameter-overrides \ EnvironmentName=msprod \ LaunchType=Fargate \ GitHubRepo=<github_repo_name> \ GitHubBranch=<github_branch> \ GitHubToken=<github_token> \ GitHubUser=<github_user> \ --capabilities CAPABILITY_NAMED_IAM
To build and deploy all services, push some changes to your repository with
[BuildAll] added to the message. To trigger specific services, add
Once finished, visit the URL of the load balancer. It is available in the LoadBalancer's Outputs tab in CloudFormation.
Fork or otherwise copy this repo to your Github account.
On the Github access token page, generate a new token with the following access:
Delete stacks in reverse order in CloudFormation. The artifact bucket and ECR repositories need to be deleted manually. So as the auto scaling group (from the EC2 console) when using the EC2 launch type.
When running locally, inspect resources by launching relevant Docker containers.
To access the database, launch a new container that will connect to our Postgres database. Then enter the password
demopsw (see the
docker run -it --rm \ --network microservices_network \ postgres:13-alpine \ psql -h postgres -U postgres -d microservices
Select everything from the messages table:
select * from messages;
To inspect Redis, connect to its container via redis-cli.
docker run -it --rm \ --network microservices_network \ redis:6-alpine \ redis-cli -h redis
Get all cached messages or show the number of total messages.
lrange messages 0 -1 get total
Access the RabbitMQ management interface by visiting
guest as both username and password.
To access the back end service, attach to its docker container from a separate terminal window. Messages from the front end will show up here. Also, standart input will be sent to the front end for two way communication.
docker attach microservices_backend
For development, run the RabbitMQ and Postgres containers with Docker Compose.
docker-compose -f docker-compose-dev.yml up
Generate static web assets for the server service by going to
web/bootstrap and running:
npm run build-server
For React development, run
npm run serve in
web/react and change the script tag in the server's template to the following: