@allenyang, I just finished reading the book on JAMstack (written by its creators). From what I can tell, this design approach may be the next best way of making apps. Between the experience of my developer friends and various case studies
LobLaw:
- 9.4x Faster To Interactive
- 92% Better performance
- 38k monthly cost savings
“The time to first load is so much faster than before… before we had to wait for the HTML file being served for 800ms and now it’s 80ms .” (more here)
and the fact that:
more than 8 percent of the internet population visits a [*JAMstack] site each month
this looks like the future of web development. Perhaps JAMstack itself isn’t the future but the central tenant of improving performance by pre-rendering HTML (meanwhile getting any CRUD operations done via APIs) is .
I know that Bubble already uses React on the front end.
You guys have also separated the concerns of the front end from the back end.
From the little I know about your tech stack, it seems like it has the essential structures in place for pre-rendering HTML like JAMstack would. Is this something you guys are experimenting with (I imagine the answer is yes)? Can you tell us the results of those tests? Or are performance issues mainly from other areas of the application?