Polymail tech stack download#

Another advantage of a SPA is that the JS frameworks and ecosystems are extremely mature.

Polymail tech stack download#

The bundle is cached by the browser, so the user will have to download it just once, at least until your next deployment. Since the bundle is static, you can push it to a CDN and get fantastic download speeds. Once youвЂ™ve downloaded the bundle, the app can be very responsive because its only constraint is the client resources and not the network (other than fetching data). There are lots of advantages to this approach. The user will download the bundle once and then navigating from one page to another wonвЂ™t require additional roundtrips to the server. The interaction with the server is to fetch data via REST calls. Single Page Application (SPA)ДЄ SPA means the entire front-end side is a single static bundle of HTML, CSS, and JavaScript. There are other options, but weвЂ™ll talk only about these because they are the ones the community and Microsoft seem focused on.

A web-assembly-based client like Blazor WebAssembly with a server-side API.

A server-rendered application like ASP.NET Core MVC, Razor pages, or Blazor Server.

A Single Page Application (SPA) with a server-side API.

There are three types of directions you can take when choosing a front-end framework.

But IвЂ™m getting a bit ahead of myself, so letвЂ™s break things down. But at least we are somewhat agreed on SPAs and MVC frameworks. The appearance of Web Assembly caused a new gold rush and now it seems everyone is writing a runtime for their favorite language. IвЂ™d love to say that that period is over, but itвЂ™s not entirely true. There was a time that a new JavaScript framework sprang to life every other day. LetвЂ™s start with choosing the front-end technology. But other than that, I love C# and Azure and I have experience with them, so working with a different cloud or a different language doesnвЂ™t make sense for me, and if youвЂ™re reading this blog, then youвЂ™re probably the same.

Why? First of all, without some constraints, I would have to write several books to cover every type of web technology. The only constraint weвЂ™ll have is that we have to deploy to Azure and we have to use. That includes the client-side tech, the backend server, the ways to deploy to Azure, the CI/CD pipeline, the database, and the login mechanism. WeвЂ™ll go over the most popular technology choices in each layer of web application development, and see their pros and cons. In this post, weвЂ™ll try to make some semblance of order. Web assembly complicates things even more now that we can create our front-end in practically any language we want. We have lots of different languages, different clouds, different server-side runtimes, and different deployment tools. There are so many different ways to create a web application today, itвЂ™s staggering.