No software project is ever complete; there is always some scope of improvement. Although this V2 variant – distributed architecture – is superior in many aspects of the V1 architecture, there are still various places where it itself can be improved.

This blog – final for this series – captures those thoughts and hopefully some of these will be implemented in later releases. If the reader has ideas, comments on how to achieve the same, I would love to hear back from you.

Wish List For Improvements

• Use Cloud init to configure the Linux servers. That will remove the need to open ports and NSGs
• change the folder name from webuser to webserver
• Use of micro-services, especially AKS clusters to create the Front-end servers
• try to scale down the servers – B1ls and check if performance is acceptable. This will reduce the cost bill to half. possibly try it with front-end web servers
• Calculate the monthly Bill and display it on the web-site
• Use of just in time access from Azure to gain access to servers
• Use of private proximity groups to improve latency between servers.
• Automate back-up – restore capability.
  • Possibly using Azure back-up service
• Monitoring and Alerting to be turned on.
• Ability for the solution to send out emails.
• Error checking during the installation of Linux scripts.
• WordPress and Blogs related issues
  • How to display the Code block in colour
  • How to display table header in WordPress