Clients, WebAPIs and Servers
The last couple of weeks have given me an opportunity to learn more about some development techniques that I had perhaps heard of and understood as concepts, but never actually seen used in practice. As a personal review for myself and bookmark, I'm going to quickly describe how these elements will be used across the MOOVPAD ecosystem to improve both security and service provision.
Rotating authentication will be applied at the app level, and rate limiting will also be applied (in different ways) to all of the client apps and back-end webAPIs. Authentication and authorisation features will also be used for user accounts, reinforced by MOOVPAD-specific features I've developed. The combination of these authentication and authorisation systems should help protect against a wide range of risks.
Real-time services will be employed for features including chat and links between users and/or professionals using SignalR. and this will help reduce the load on data services as well as improve user security and privacy, since there will be less demand to store this information in MOOVPAD servers. The system, including all client apps, webAPI's and servers will also be thoroughly logged for error and process reporting. WebAPIs will be built with specific roles to handle specialised functions like reporting on global averages for user metrics and the running of background system tasks, and in combination with the nature of Blazor WASM, will help provide a similar approach to Redis memory cache and Hangfire automation as concepts (in theory, still to be tested).
Global exception and risk event reporting will be applied to all levels and systems of the MOOVPAD ecosystem, and these will be monitored in real time to help prevent and/or manage such incidents, with a CI/CD approach at the core of these approaches (and others). I'm still learning more about all of these topics and others, but at least I now have a toolset ready to go and a plan for upgrading existing MOOVPAD code and system architecture overall.
And I only lost 95% of my brain function to get here 🙂
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.