DEV Community

Web apps - my mental cheat-sheet

costica on January 21, 2023

Intro This article is part of the “Continuous Delivery: HTML to Kubernetes”. While I can’t wait to get into the nitty gritty details of...

Read full post

Alexandru Bucur • Jan 21 '23

I think it's an interesting high level overview. It would be really useful for a lot of tech recruiters so at least they get some level of understading of what they can also ask candidates in a first screening.

Michael • Jan 23 '23

Love how you add in scaling, a lot of projects start as POCs and build up over time without any look into how this will need to be worked on as they grow until you hit a wall. Which then requires severe review or rearchitecting what has already been done.

leob • Jan 22 '23

Great overview, good read, well done!

Shubh Sharma • Jan 26 '23

Really helpful

MrZodoxVpython • Jan 28 '23

love you!

senthil kumar • Jan 28 '23

Really loved the way it explained . Easier to co-relate and understand the concepts .
Clearly able to see the amount of effort goes into this article.

feldmanovitch • Jan 22 '23

really great overview!! tks for putting all that together :)

costica • Jan 22 '23

Glad you found it useful :D

Jan Peterka • Jan 23 '23

Really nice explanation, thanks!

I understand you needed to keep it simple, but I would like to mention here approach that also adresses negatives of Server generated site that you described:

For the server-side generated html, for each request, the server needs to do extra work to process it and return the entire html that will be rendered by the browser. That means extra work on the server plus a huge response (the entire html markup) being sent over the (possibly unreliable/slow) network. To top it off, the users see a blank page while the browser loads the new page.

Using fetching and some smart server rendering, this can be easily improved. Does it make developing/the app more complex. Well, it can, but with help of something like Turbo, it also can just enable lowering the load for server/browser/connection for most of request, while still keeping simplicity of Server-side generation. So, I believe it's important to know about these options before jumping to SPA. There are of course cases when SPA makes sense, but I would argue against using it primarily to lower server load or response size.

Arjun Porwal • Jan 22 '23

Awesome Post ! By the way can you let us know what software/tool did you use to make these graphics ?

costica • Jan 23 '23

Pro tip: you could've "stolen" this information yourself: if you click any of the " (Click here for higher-quality visuals)" links, you can see in the URL bar the app is pointing to viewer.diagrams.net :)