Caching & Load Balancing
Earlier today, we looked at the forking of the MOOVPAD WebAPIs and repositories, as well as how all the different components currently being developed work together. Since then, I've been learning and adding even more to the reverse proxy and downstream webAPI templates. Custom configuration files, which I believe I can updated dynamically with JSON input, have been built.
I've also written some middleware components to handle memory caching at the gateway and downstream webAPI levels, as well as implemented the normal output caching on individual endpoints and controllers. These approaches combined will really help improve the performance of the webAPIs and the system overall. I may still bring in third-party packages if needed later. In previous work, I also incorporated rate limiting, and I'll be bringing this in too. The work at the moment is focused on load balancing approaches. And all of this work is being documented throughout and uploaded to the RefLib repo for future team use.
Once these load balancing policies are added and configured correctly, I'll then finish off with the last goal for the day of passing the authentication and authorisation from the reverse proxy through to downstream webAPIs. The elements discussed here and above will help keep MOOVPAD internal systems and UX for app users optimal, and further help with security through the entire service pipeline.
At least... that's what my "sooooo over it" brain says lol 🙂
Stay awesome,
EMH
HOW MOOVPAD IS BEING BUILT
For the overview of how MOOVPAD apps are being developed, the reasoning behind particular decisions during development, policies, and more in relation to all the technical things, please see the link to the left.
This will be an ongoing work in progress, and will always be linked to the bottom of each upcoming Blog post.