2.4

Release 2.4

Changes

Scrum-210 - As a developer, I want to have an API gateway in place, so that all requests and queries from the main website can be routed through a single entry-point for the overall solution.

• Added a repository for the API gateway.
• Defined and routed the endpoints from the microservice through the API gateway to the main site on the gateway.
• Made a request to the microservice to retrieve the information.
• Sent the information through the gateway.

Scrum-211 - As a developer, I want to have detailed monitoring and logging within the API gateway, so that I can easily troubleshoot and have more detailed insight into the traffic coming through the API gateway.

• Added a try catch for data serialization, only logged if unsuccessful.
• Added a try catch for connecting/sending data to the website successfully, logged both if success or failure.
• Added a try catch for receiving data from microservice, logged if successful or fail.
• Added timestamps to the existing logger.

Scrum-214 - As a developer, I want to test the API gateway extensively, so that I can ensure it is working as intended under high traffic.

• Added a separate production instance (AWS, etc) for testing.
• Added a docker container for the API gateway.
• Pushed containers onto the instance.
• From instance, tested the website with the gateway.