I will need it to be threaded so that i can pull data simultaneously.
What language should I use.
1) Ruby 2) Scala 3) Java 5) PHP
I know Ruby PHP and Java well.
Thanks
1–10 of 10 posts
I will need it to be threaded so that i can pull data simultaneously.
What language should I use.
1) Ruby 2) Scala 3) Java 5) PHP
I know Ruby PHP and Java well.
Thanks
http://www.playframework.org/documentation/1.2.3/jobs
Alternatively you could simply use Quartz alone.
It would be polite to put to least a hint of your question in the title so people know what it's about.
If you know java and scala, I would recommend you to give Play framework a try. It is extremely simple and fast to set up and develop with, plus it uses Quartz scheduler library for the jobs. http://www.playframework.org/documentation/1.2.3/jobs Alternatively you could simply use Quartz alone. http://www.quartz-scheduler.org
You can use play's WS class to make asynchronous HTTP calls from your server, and it integrates nicely with MySQL or your database of choice too. I think it uses Hibernate under the hoods, but leverages all its power while simplifying configuration and usage.
You can use Play with Scala, and if you do so, there is a nice database layer called Anorm.
If you know java and scala, I would recommend you to give Play framework a try. It is extremely simple and fast to set up and develop with, plus it uses Quartz scheduler library for the jobs. http://www.playframework.org/documentation/1.2.3/jobs Alternatively you could simply use Quartz alone. http://www.quartz-scheduler.org
And for the rest of your needs, Play gots you covered too... You can use play's WS class to make asynchronous HTTP calls from your server, and it integrates nicely with MySQL or your database of choice too. I think it uses Hibernate under the hoods, but leverages all its power while simplifying configuration and usage. You can use Play with Scala, and if you do so, there is a nice database layer called Anorm.
Earlier quoted context omitted.
And for the rest of your needs, Play gots you covered too... You can use play's WS class to make asynchronous HTTP calls from your server, and it integrates nicely with MySQL or your database of choice too. I think it uses Hibernate under the hoods, but leverages all its power while simplifying configuration and usage. You can use Play with Scala, and if you do so, there is a nice database layer called Anorm.
I see Play is web dev framework. As far as my system is concerned I dont need to have a full web app. The system just needs to sit in the background read the database and then request 2-3 API's for data and put that back in the db. I expect a lot of writes to the database. I am reading about Play's support for jobs. Do you still think Play is the way to go ?
As I said, you can always use just Quartz for the jobs (that's what Play uses anyway), and create your own Data Access Layer or use an ORM, or what you like.
Earlier quoted context omitted.
And for the rest of your needs, Play gots you covered too... You can use play's WS class to make asynchronous HTTP calls from your server, and it integrates nicely with MySQL or your database of choice too. I think it uses Hibernate under the hoods, but leverages all its power while simplifying configuration and usage. You can use Play with Scala, and if you do so, there is a nice database layer called Anorm.
I see Play is web dev framework. As far as my system is concerned I dont need to have a full web app. The system just needs to sit in the background read the database and then request 2-3 API's for data and put that back in the db. I expect a lot of writes to the database. I am reading about Play's support for jobs. Do you still think Play is the way to go ?
http://www.playframework.org/documentation/api/1.2.3/play%2F...
However, RabbitMQ might be too much overhead for what you want to do. With Ruby, specifically, I've had a good deal of experience with Resque, which uses Redis (key-value store) as a queueing system, much like RabbitMQ. It's easy to set up, and gets the job done just as well.