![]() We took this a step further and introduced Edge computing such as Vercel's Edge Network. However, the side effect was that we also distributed loading spinners across the web. This improved loading times - the Time to First Byte (TTFB) - of web applications, but if the application required dynamic data, e.g., from an API or database, the application needed to make another request for the data. We - developers - attempted to fix this with the JAMstack architecture, where static assets, such as HTML, CSS, JavaScript, and images, would be distributed across the globe in a Content Delivery Network (CDN). While this deployment pattern worked fine, the problem this created was that a user located on the other side of the globe would experience slightly longer response times. Traditionally, applications would be deployed to a single region or data center, in either a virtual machine, Platform as a Service (PaaS) like Heroku, or Functions as a Service (FaaS) like AWS Lambda.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |