e1 Testing a simpler version of an API gateway, NGrok, and service-based API requests

Описание

In this video I am going to be working on testing a web server cache. The code is mostly done, but it needs to be made more reliable first before building API's on top it.

The end-goal is to have an architecture where the web server cache can be queried from any server. An alternative to this would be to hard-code the ports for all of your services into a flat-file. A more expensive version of this would instead register each service with an API gateway, and the API gateway would maintain the server cache index while proxying requests out from a single address.

You always look for short-cuts when developing software. Since this work lives in the Microcloud product, the goal is to create a reusable tool that other developers can use. You normally would be best off to code a flat-file pre-assigning ports and then using that flat-file as a lookup.

The steps that will proceed here would all be considered solving for very difficult problems, required dozens of hours of prep, and are at risk for being over-engineered in their current state. The product-based objective is to have backends enabled across services, and in the interim relying on a tool like NGrok to get services established over DNS will help tremendously with that effort.