In this article we will see how to design web app to serve static content files like images, java scripts, css etc… files from AWS S3. Generally we will use Apace/Nginix as the software load balancer and some times we will use the same to serve the static content to reduce the traffic to the application. But, the number of requests will be overloaded to Apache/Nginix and the serving of the static content will become bottleneck to the application performance. The below diagram will depict the traditional architecture.
We will modify the above architecture to make use of AWS S3 to serve the static content. Serving of the static content from the AWS S3 is highly available, fast and reliable. AWS S3 has SDK’s for all the prominent languages to push the content to S3 pragmatically. The below design will depict the usage of AWS S3 as the static content server.
Happy Cloud Computing !!!
Siva Janapati is an Architect with experience in building Cloud Native Microservices architectures, Reactive Systems, Large scale distributed systems, and Serverless Systems. Siva has hands-on in architecture, design, and implementation of scalable systems using Cloud, Java, Go lang, Apache Kafka, Apache Solr, Spring, Spring Boot, Lightbend reactive tech stack, APIGEE edge & on-premise and other open-source, proprietary technologies. Expertise working with and building RESTful, GraphQL APIs. He has successfully delivered multiple applications in retail, telco, and financial services domains. He manages the GitHub(https://github.com/2013techsmarts) where he put the source code of his work related to his blog posts.
Nice write up.