I’m currently in the research phase for a (very) small database application.
It’s for a local charity which only has 3 or 4 client machines which will be running the system – however in order to move some extraneous logic away from the clients, I’m leaning toward using a three-tier architecture (there is data that is constantly read-through and updated when appropriate, that the client does not need to know about)
i.e. Client <-> Server logic <-> Database
Whilst I’m competent with Java itself and a few frameworks/libraries, I’m not particularly familiar with what frameworks could help me here. Obviously I’ll be using JDBC for the database half, but the communication between client and server is the stumbling block at the moment – I don’t really want to go anywhere near raw sockets, for example (overkill, or at least, another solution must exist)
I’ve asked a few developers I know about their opinions on what APIs to use, and whilst they’ve been very helpful, I’m still not too sure where to go. So far I’ve heard about RESTful stuff, SOAP, COBRA and a whole bunch of other technologies. SOAP is the main one that caught my attention (as there are some good examples of using it with normal applications rather than just with the web) but I’m still not sure where to go – it doesn’t seem particularly appropriate for a general purpose app like this one (EJB also popped up but I heard a lot of hatred aimed at it – is this deserved?)
It feels as if in order to find out the ‘best tool for the job’ I actually need to learn each one in its entirety to ‘get’ them (which is obviously impractical)
Can anyone give me guidance as to how to choose APIs like these (when I haven’t used them before) or give me information about a few common ones, or is it really just a case of experimenting with lots of them to see which fits best?
Or maybe I’ve totally missed the mark and there’s a framework which is aimed at this exact situation with no obvious cons?
Thanks very much for any help.
Completely forgot to mention what it actually does: It isn’t terribly complex – the charity runs a transport scheme, so it holds details of drivers, clients, driver mileage records etc. for viewing and editing The only real complexity comes with the drives, since drivers can be assigned to repeating (ongoing) drives that could foreseeably continue ‘forever’. But each instance of an ongoing drive must be unique because they can be cancelled or edited individually
The main reason I’m angling for 3-tier is because being a charity (with many older volunteer computer users who aren’t terribly ‘savvy’) I may well be updating the UI quite frequently to iron out bugs and bits that aren’t very clear to novice users. So my plan is to get the backend between the server and DB absolutely ‘bulletproof’ first of all, and then pour all my focus onto the UI so I can continue to develop and iterate it without worrying about the backend (also since I will be developing pieces of it remotely, focusing updates on client side is slightly simpler)
All these attributes probably shout out ‘do a web based system’ – the snag here is that they’re after all kinds of tricky integration with some applications they already run, which I’m not confident I can get done (properly) with a web app.