You are visiting a serverless blog! You can see below a sample request flow for this blog. AWS (Amazon Web Services) owns the servers that house the blog's content and is responsible for serving it when requested.
Here is a basic introduction to Serverless Architectures.
The following diagram shows the flow when resources are fetched from AWS S3 because they have not yet been cached at AWS CloudFront (or if the existing CloudFront cache was invalidated).
The following diagram shows the flow when resources are cached at AWS CloudFront.
The user's DNS requests are served by Amazon Route 53, a highly available Domain Name System Service. Network traffic is routed to infrastructure running in AWS.
Static content is delivered by Amazon CloudFront, a global network of edge locations. Requests are automatically routed to the nearest edge location, so content is delivered with the best possible performance.
Static content like html, js, css, and images are stored on Amazon Simple Storage Service (S3), a highly durable storage infrastructure.
Because the sites contents is largely static, CloudFront does an excellent job of serving back cached files. Also, since the content is largely either tested technical material or based on my experiences, I rarely need to change content, so cache invalidations of cloudfront are few and far between. This has helped me keep the running cost of the site to less than a dollar per month for the last few years.