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.
Software Manager, Agile Aficionado, Tech Dabbler, and Public Speaker. A lifelong learner, the prospect of something new and coffee are what get me up in the morning.
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.
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.
Full Stack Engineer | 6+ yrs crafting with MERN, UI enthusiast & product builder. Love creating sleek, high-performant apps, leading teams & diving into latest tech. Constantly building & exploring !
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 :)
Full Stack Engineer | 6+ yrs crafting with MERN, UI enthusiast & product builder. Love creating sleek, high-performant apps, leading teams & diving into latest tech. Constantly building & exploring !
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.
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.
Great overview, good read, well done!
Really helpful
really great overview!! tks for putting all that together :)
Glad you found it useful :D
love you!
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.
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:
Using
fetchingand 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.Awesome Post ! By the way can you let us know what software/tool did you use to make these graphics ?
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 :)
I'm really impresive about this huge article with awesome diagrams,
Could you reveal for us how to make the hand-draw style diagrams by diagrams.net like yours ???
PS: got that:
diagrams.net/blog/rough-style
thanks
I'm using app.diagrams.net/ at the moment (formerly known as draw.io)
Haha thanks for the info !
That must have been a lot of work to make all of this , Hats off.
The read was awesome. But it would be better if you can explain the SPA and SSR SPA in depth. Keep it up @costica 👏