Microservice Architecture with Multiple Languages

The idea for this project is to show a case for applying Microservice Architecture using multiple languages.

Most all services are built in Java with Spring Boot 2 + Webflux + MongoDB but there are other services using NodeJS, Kotlin, Python and Go.

The web application is using React and a beta version using JHipster.

Feel free to create a new microservice using a different language(Ruby?, C#?), just please following the minimal requirements:

Create a new folder on root and put your code
Add a minimal documentation
Add a Rest API
Add JWT Validation
Add Tests
Add Dockerfile
Add MongoDB or some other NoSql
Add Consul Client(if possible)

PS: A better approach would be a microservice per repository but for simplicity all microservices are in the same repo.

If you want to contribute please check TODO List.

Inspired by the book Microservices Patterns(Chris Richardson - @crichardson).

Microservice Patterns
Prerequisites
Microservice Diagram
Installing all services using Docker Compose
Docker Commands
Manual Installation - NOT RECOMMENDED
Accessing React Web App
List of default users
Kubernetes - Google Cloud Platform
~~Travis CI/CD~~
Github Actions CI/CD
TODO List
References
Postman Collection

Microservice Patterns

The following list of Microservice Patterns was applied so far.

Server-side service discovery - Consul
API Gateway - Spring Cloud Zuul
Externalized configuration - Consul using Spring Cloud Config yaml format(with spring profiles), more details look at docker/spring-cloud-config
Exception Tracking - Spring Boot Admin
Access token - Spring Oauth2 with JWT
Health Check API - Spring Boot Actuator Starter
Distributed tracing - Jaeger
Application metrics - Spring Micrometer Prometheus
Database per service - MongoDB an instance per service
Shared database - Redis for sharing http sessions

To know more about each pattern look at Microservice Architecture

Prerequisites

JDK 1.8
Maven 3
Docker 17.05.0-ce+ - Not necessary but recommended otherwise the services should run by command
Docker Compose 1.23.2 - Not necessary but recommended otherwise the services should run by command

Microservice Diagram

Installing All Services using Docker Compose

The easiest way to run all microservices is using docker-compose, run the following commands:

On root folder first need to generate the docker images.

# at once for building the docker images
mvn clean install jib:dockerBuild

On docker folder run all microservices

docker-compose up -d

Docker Commands

To see logs for a specific docker container:

docker logs -f SERVICE_NAME

PS: Service names are on docker-compose.yml -> container_name

To execute a command inside the container:

docker exec -it week-menu-api sh

To stop and remove all containers:

docker-compose down -v

To restart/start/stop/remove specific container:

docker-compose restart SERVICE_NAME
docker-compose up SERVICE_NAME
docker-compose stop SERVICE_NAME
docker-compose rm SERVICE_NAME

Manual Installation - NOT RECOMMENDED

If for some reason you cannot install docker/docker-compose you can run all services manually using the following command for Java applications.

mvn spring-boot:run -Dspring-boot.run.arguments="--server.port={PORT}"

To run NodeJS and React applications on folders nodejs-service and react-webapp:

sudo npm install

sudo npm start

Accessing React App

To access React Web App.

Default Users

Following the list of default users:

admin@gmail.com/password - ROLE_ADMIN

master@gmail.com/password123 - ROLE_PERSON_CREATE, ROLE_PERSON_READ, ROLE_PERSON_SAVE

anonymous@gmail.com/test - ROLE_PERSON_READ

Kubernetes - Google Cloud Platform

The code is deployed at Google Cloud Platform, ~~to access it go through https://spendingbetter.com~~.

Following useful commands for kubernetes

Installation

#helm create ingress - RBAC enabled
kubectl create serviceaccount --namespace kube-system tiller
kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller
helm init --service-account tiller
helm list
helm init --tiller-tls-verify
helm init
kubectl get deployments -n kube-system
helm install --name nginx-ingress stable/nginx-ingress --set rbac.create=true --set controller.publishService.enabled=true

#helm list
helm list

#create tls
kubectl create secret tls ingress-tls --cert /etc/sslmate/www.spendingbetter.com.chained.crt --key /etc/sslmate/www.spendingbetter.com.key

#create generic certs
kubectl create secret generic spendingbetter-p12 --from-file=/etc/sslmate/www.spendingbetter.com.p12
kubectl create secret generic spendingbetter-crt --from-file=/etc/sslmate/www.spendingbetter.com.crt
kubectl create secret generic spendingbetter-jks --from-file=/etc/sslmate/www.spendingbetter.com.jks

#list certs
kubectl get secrets

#list specific cert
kubectl describe secret ingress-tls

#show ingress
kubectl get ing
kubectl describe ingress


# Istio
# Get Grafana Configuration
kubectl get service grafana --namespace istio-system -o yaml

# Update Grafana Configuration
kubectl edit service grafana --namespace istio-system

Deployment

cd kubernetes

#create docker image
docker tag eureka-server:latest eu.gcr.io/spring-boot-gke-243520/eureka-server:4.0
docker tag docker_react-webapp:latest eu.gcr.io/spring-boot-gke-243520/react-webapp:6.0

#push docker image
docker push eu.gcr.io/spring-boot-gke-243520/eureka-server:4.0
docker push eu.gcr.io/spring-boot-gke-243520/react-webapp:6.0

#Deploy
kubectl apply -f deployment-admin-server.yml

#Undeploy
kubectl delete -f deployment-admin-server.yml

#see logs
kubectl logs admin-server-XXXXX -f

#exec command
kubectl exec -it redis-5b4699dd74-qckm9 -- sh

#show all pods
kubectl get pods --show-labels

#create config map
kubectl create configmap prometheus --from-file=../docker/prometheus-prod.yml

kubectl create configmap grafana-dashboard --from-file=../docker/create-datasource-and-dashboard.sh

kubectl create configmap grafana-datasource --from-file=../docker/grafana-datasource.yaml

#port forward
kubectl port-forward $(kubectl get pod --selector="app=eureka-server" --output jsonpath='{.items[0].metadata.name}') 8761:8761

#delete specific ingress
kubectl delete ingress ingress-gateway-forward-https

#cpu usage
kubectl get nodes --show-labels
kubectl describe nodes gke-your-first-cluster
kubectl top nodes