Dynamic/SPA/Static Websites

-


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, Vue.js, React.js frameworks are popular for building SPAs

Static Web Apps

Static site generators like Next.js, Hugo, Gatsby, Jekyll, etc. pre-render or generate full html pages with data during compile time and stores them on a server/storage(Azure Storage/AWS S3). 

Consider static web apps when content does not change that often, like blogs, company public portals etc.



Comments

Post a Comment

Popular posts from this blog

Offline Apps Patterns and Tools

-
Apps capable of running offline provide a great user experience even when there's slow/unreliable or no network/internet available. They also minimize data usage and save battery power when run on mobile devices. Design Considerations: Upfront, both front and back end must be designed to work offline.  Think about features that cannot work in offline mode. Single users using the app on multiple devices. Automatically sync data (uni/bi-directional) stored locally on the device with the central database once the app is able to connect to the internet.  If the app is allowed to be used from multiple devices, conflicting data changes made by users and any data sync conflicts need to be handled. To make UI work offline, in the case of Mobile applications, there's nothing to do, but web applications will have to use something called service workers. By implementing a service worker, you can turn a regular web application into a Progressive Web App, making it downloadable and install...
Read more

Private Cloud Platforms

-
The below services let you   take public cloud infrastructure, private data centers or mix both to build a private cloud on-prem. AWS Outposts and Azure Stack are quite similar in that they essentially take public cloud computing services and extend them into on-premises data centers.  Using these frameworks, services available in public clouds like AWS EC2 , or Azure Virtual Machines can be run on on-premises data centers. You can also use the same monitoring and management tools that you would in the public cloud. Azure Stack Hub Azure Stack Hub brings core cloud services to customers' data centers, like virtual machines, storage, networking, VPN gateway and load balancing, as well as services like functions, containers and database. Certified hardware can be purchased from  a variety of partner vendors, such as HPE, Dell EMC, Cisco, Huawei and Lenovo.   Users need to manage their infrastructure, but professional support from Microsoft is available as part of the p...
Read more

Application Delivery in the cloud

-
Traditional load balancers have lately evolved to become intelligent application delivery controllers (ADC) which implement various techniques to improve performance along with balancing load across a group of backend servers. Some of the techniques include caching content, compression of assets (js files, images etc.), taking over SSL related process from web servers, providing security from DDoS, SQL injection, XSS etc.. ADCs are like one-stop-shop for providing performance and security.  Load balancers for non-HTTP(s) workloads: Azure Traffic Manager: Is a global non-HTTP(s)/DNS load balancer. DNS load balancers provide IP address of an healthy endpoint based on the configured rules. The endpoint can be an application gateway or a load balancer depending on whether SSL offloading or application layer processing is required or not. Azure Load Balancer: is a non-HTTP(s) global (cross-region)  load balancer (aka network load balancer) operates at layer 4 (transport laye...
Read more