Answer the question
In order to leave comments, you need to log in
Development of software architecture (DB + web). What options would you suggest?
Hello colleagues.
It would be desirable to hear as it is better (and on what) to implement software at the following initial conditions:
1. There is a database (Oracle DBMS). Physically dedicated server.
2. Clients access the database using a web server. Also a physically dedicated machine.
3. There is also an application server (and it is dedicated), specific calculations are performed on it using scripts in C. Requests come from a web server, data is naturally taken from the database. The calculation results are sent to the web server. The amount of data transferred from node to node is not very large, well, that is, it is not gigabytes, but quite a few megabytes. Well, maybe one and a half to two dozen with complex operations.
The question is, how best to organize communication between these links and what approaches to use?
What I see now is the solution:
1. Place php scripts on the application server that would call sish programs and give the result to the requester via REST in the form of JSON packages.
2. On the web server, also use php to work with the database and requests to the application server.
3. Create a UI, for example, on bootstrap (but it doesn't matter what) and use js to work with php scripts.
4. On js, create some kind of miniframework for parsing and processing JSON packets from php scripts.
Am I thinking in the right direction? Or is this all bullshit? Can any js or php frameworks tell me to solve such problems? Thank you.
Answer the question
In order to leave comments, you need to log in
I suggest:
Think in the right direction.
For the client side, I use Durandal + KnockOut (the alternative is Angular), decorating it with bootstrap.
I can’t tell you about the server php part, I work on .net.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question