Algoclinic Blog's Serverless Architecture

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 are 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).

Blog Request Flow when CloudFront does not have requested resources cached
Request Flow When AWS CloudFront Cache Miss Occurs


The following diagram shows the flow when resources are cached at AWS CloudFront.

Blog Request Flow when CloudFront has requested resources cached
Request Flow When AWS CloudFront Cache Hit Occurs


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.

Blog Technical Architecture
Technical Architecture