This hand-in demonstrates:
Ocelot.json specifies a new endpoint, and hides the two existing ones from the user. It also provides us with some north/south security
I have used Polly to implement a bit of fallback
I specified the GatewayService, UserService and TweetService in Kubernetes. It works, and every service is up and running:
I have implemented a JwtTokenService to do all it's magic and help me setup east/west security. The TweetService demands a valid token in order to hand out anything else than an error
The MonitorService has been implemented as a Sidecar
- A UserService implemented as an API with basic CRUD controls for users
- A TweetService implemented as an API with basic CRUD controls for "Tweets"
- A MonitorService that showcases a "Side-Car" Design Pattern
- An AuthService that helps setting up authentication between services