Single tier Architecture
All services that are needed to build an application will be configured inside a single server that also handles requests and responses.
Basically, an application needs a webserver(httpd, nginx etc) ,app server(JBoss, Tomcat, Glassfish) and finally database server(mysql, oracle, mongoDB etc) to work effectively, so in a single server architecture all the above mentioned components will be configured in a single server. The server's private IP will be used for all communications between the web, app, and database.
In a single-tier architecture,all the services will be on the same machine using the same resources, which can create an availability risk. If the server is down, then the entire application will be down. Single tier is suitable for simple applciations or sites with low traffic.
Below is a basic diagram of a single tier architecture.
You can see from the above diagram that user requests are routed through the firewall to a single server, and that all communications take place solely between the user and the server.
Advantages
1) Cost effective
2) Simple and uncomplicated design
3) Faster communication between App, Web and Database services
Disadvantages
1) Less Availability
2) Higher down time
Cheers🥂🚀
Keep Learning!
Top comments (1)
That's it!
I usually use this architecture for side projects to begin with or even for client webApps (be they PWAs or not).
I've recently found Next JS pretty convenient for that, as it provides a place to put your
/api/endpoints which you can then extract easily into a different Node JS servers if needed.Following you to read more about different architectures! 😁