I'm currently in the research phase for a (very) small database application.
This is for a local charity that has only 3 or 4 client computers that will run the system, however, in order to move some extraneous logic away from clients, I tend to use a three-tier architecture (there is data that is constantly updated and updated, when it is necessary that the client should not know about him)
i.e. Client ↔ Server Logic ↔ Database
While I am competent with Java itself and a few frameworks / libraries, I am not very familiar with what frameworks can help me. Obviously, I will use JDBC for half the database, but the connection between the client and the server is a stumbling block at the moment - I really do not want to go anywhere near raw sockets (for example, (overkill, or at least another solution should exist)
I asked a few developers whom I know about my opinions on which APIs to use, and although they were very useful, I'm still not too sure where to go. So far I have heard about RESTful materials, SOAP, COBRA and a number of other technologies. SOAP is the main thing that caught my attention (since there are some good examples of using it with regular applications, and not just with the network), but I'm still not sure where to go - this does not seem particularly suitable for the general (EJB also appeared. but I heard a lot of hatred aimed at him - does it deserve it?)
It seems that in order to learn the “best tool for work”, I really need to learn to everyone as a whole in order to “get” them (which is obviously impractical)
- , API ( ) , ?
, , , , ?
.
:
, : - , , , .. . , () , . ,
, 3- , , , ( -, "" ), , . , , "", , , (, , )
, , " -" - , , , , ( ) -.