9 Comments
User's avatar
Swapnil Wadhankar's avatar

This is the kind of articles we need. Thanks man appreciate the hard work you put in these articles. Gave so much clarity on the approach.

Mohit Bodhija's avatar

this is really helpful

Dharmaraj Rathinavel's avatar

If web servers handles the request from the client and app server has the bussiness logic, then how web and app servers will communicate? Also, what is the need for different servers? Instead can we have app servers behind load balancers?

sankarsh's avatar

webserver mainly have the static content like HTML, CSS, JS and Images. whereas the ApplicationServer will be executing the application logic and processing business logic.

Jake's avatar

Not exactly, for example you have a website, all your contents are hosted in GoDaddy, then that's your webserver. Your user is accessing the website contents (HTML, JS, CSS) in the GoDaddy.

Your JS code sends request to your backend server (application server) to retrive data.

Nitesh Kumar's avatar

I think the order should be slightly different. Before jumping into HLD, we should list all the APIs. Based on the APIs list, we can separate the concerns, group the APIs, and eventually we can identify, how many micro services are required along with their responsibilties.

javinpaul's avatar

great article, loved it

Atif Afridi's avatar

❤️❤️❤️🫡