CODEWITHSUNDEEP
javadatabaseweb-serviceswebserver
Philipp
Philipp

Reputation: 535

Systemdesign: Webserver, API and Database

Currently i have a website offering some product. The webserver sits on the same system as the database and directly accesses it to retrieve the required information for the HTML frontend. Now i think it is good to separate the database from the webserver via an API server. The reason why i want to use an API server is that it might be possible that future applications, other than the website, will need access to the information on the system.

The system which i want should consist of the following components:

So basically what i have in mind is that i want to build my website on top of that API server. The user will register/login/... over the website and the website implementation will internally query the API server as a webservice on behalf of the user. The API server would then return the data from the database. That way the HTML frontend is just an application using the API server and will never itself be in direct contact with the database.

I think that this is an often encountered problem for which a good solution exists. I am unsure if this solution is the way to go though. Could you help me out and/or point me in the right direction from here?

Thank you.

Upvotes: 0

Views: 88

Answers (1)

Ivan
Ivan

Reputation: 847

As far as I know, it is not advisable to have a separate API server for a couple of reasons: decreasing performance and increasing compexity of a system. So basically you should avoid this type of solution for as long as possible.

You should definitely read M. Fowler: "Enterprise Architecture Patterns" for inspiration.

Returning to your question: have you considered making this API layer as a module (library)? If I haven't convinced you, try reading Java RMI documentation (http://www.oracle.com/technetwork/java/javase/tech/index-jsp-136424.html)

Upvotes: 1

Related Questions