Random Technology Posts

Azure first came up with static websites in storage then released Azure Static Web App Service. Azure Static Web Apps Integrated with GitHub actions - deployed as soon as code is checked in. Custom domains names with free SSL cert Supports Azure Functions Built in security policies Azure Storage Website Cheap Use CDN for custom domain names and SSL I've used Azure Storage website for : hosting static pages generated by DocFX. You don't really need a vanity domain for an internal document site. Click-once deployment packages for desktop applications

Websites contain static content (html, css, images etc.) whereas web applications are more complex and interactive, i.e. user read and update data. Dynamic Apps Web server creates html pages (Server Side Rendering) with data using a  server-side programming language  and sends it in response to requests coming from the clients (browser). The server interacts with APIs or databases directly to get the data for the pages. Use ASP.NET Core MVC, Java Spring frameworks to build dynamic web applications. SPA (Single Page Applications) The web server (you could use a CDN to deliver too) on the first request from the client returns a main/base html page (like a container) along with all the JavaScript's needed to generate subsequent html pages (Client Side Rendering) on the client side(browser). JavaScript's call backend APIs for required data to weave into the html.  SPA is good choice for SaaS business applications because you don't really need search engine crawling. Angular, ...

Architecture diagrams coming soon....

After working with BizTalk for a long while, I had to work with MuleSoft Anypoint platform on a recent project. Intrigued, I started reading about it and signed up for their free courses online. I cleared their MuleSoft Certified Platform Architect Exam after finishing the recommended courses. Alright, what got me going with it was the platform's approach to building enterprise system networks via APIs. The platform apart from providing all the tools and best practices also provides an overall approach to help an enterprise succeed in building API-connected systems that reduce silos and deliver solutions faster. The idea is to productize the APIs that can be consumed internally and externally. Let's say you have a backend legacy system with a database that nobody really understands except for few folks who maintain it. This is the process,  1. Few folks who understand the legacy system database write an API specification in OAS or RAML first using MuleSoft Anypoint Designer. ...