Re: Storing data periodically on remote server
- From: Arne Vajhøj <arne@xxxxxxxxxx>
- Date: Thu, 09 Oct 2008 22:24:11 -0400
Peter D. wrote:
On Oct 7, 6:25 am, carmelo <csa...@xxxxxxxxxx> wrote:I have to develop a java application to send every 10 seconds a tuple,
made of 3-4 fields, to a remote server. I thought to proceed in this
way:
- server side: mysql dbms (for storing clients transmitted data)
- client side: java application which makes an odbc connection to the
remote mysql db
The expected workload is quite high, in fact, there will be about 100
clients, each of them send data on time interval of 10 seconds.
Do you think is it a good solution?
I don't know if connecting to the DB directly is a good idea. I would
recommend creating a web service to accept the data instead. The
client will connect to the web service and send the info. The server
side web service will then connect to the DB and do what it needs to
do.
With a web service you can even give your clients the option of coding
their own solutions with any language. Also, it gives you free reign
on your DB server since the web service will abstract it from the
users. If you want to change DBMS you just need to modify the web
service and not every single client.
The extra tier makes it easier to switch database and the use of
SOAP/HTTP as transport makes it possible to write clients in
other languages.
But are those features needed ?
If they are, then it is a good way.
But if they are not then it is just adding lots of
unnecessary complexity to the solution.
Arne
.
- References:
- Storing data periodically on remote server
- From: carmelo
- Re: Storing data periodically on remote server
- From: Peter D.
- Storing data periodically on remote server
- Prev by Date: Re: Storing data periodically on remote server
- Next by Date: Re: Storing data periodically on remote server
- Previous by thread: Re: Storing data periodically on remote server
- Next by thread: Re: Storing data periodically on remote server
- Index(es):
Relevant Pages
|