...
- this is just happy flow after obtaining a valid JWT token
- communication with KC is transparent to validate a JWT token
- the services based on spring boot with spring security (when configured correctly) automatically does the authorisation automatically
Notes:
- this is another basic image of how our services are deployed
- for each environment, we have two machines (blue, green) where our services are deployed
- each machine has a full copy of the stack deployed in docker containers, the only difference is that blue will also contain K.C
- the ELK stack and monitoring services are on separate machines
- the external facing load balancer is the entity that decides where the request is forwarded to
Notes:
- a further look into a single machine where the services are deployed (green in this case)
- communication happens over the docker network
- what happens when a service goes down
Notes:
- what happens when profile goes down?
- what is a cascading failure
...
- K.C goes down, whole system is no longer available
- We only have one BDDB. Not the microservices way, another single point of failure
- Read replicas not in place
- Can the LB go down or struggle with traffic
- Profile service goes down we get cascading failures
- Docker network stopping us from communicating to other instances of a service
...