Java Scheduling Gets a Shot in the Arm, Courtesy of Terracotta
Terracotta continues its open source project acquisition tear today, bringing the the Quartz Scheduler project into it's fold. This latest move follows the acquisition of the EhCache project back in August. According to Terracotta, the acquisition of Quartz helps them meet the needs of customers in virtualized environments. Much of the immediate development will be focused on adding more support for those runtimes.
Quartz founder James House, had this to say about the acquisition:
"I am excited to bring Quartz into the Terracotta family of products and to extend the investment in this technology," said James House, founder of Quartz. "This acquisition will benefit both communities. In the short term, Quartz users will get a cost-effective and easy clustering solution; in the long term, large-scale Terracotta users will be able to easily add Quartz to manage distributed workloads."
For most users of Quartz, the acquisition will have little impact other more development activity. There will also be new enterprise support options for users of Quartz. The license of Quartz will also not change, according to Terracotta.
The new website of Quartz, http://quartz-scheduler.org, has more information about the acquisition along with the latest bits available for download.
With this latest move, Terracotta appears to be following the time honored tradition of open source companies like Spring and JBoss by acquiring other open source projects to supplement their own products. What else do you think would be a good fit for the Terracotta umbrella?
- Login or register to post comments
- 3187 reads
- Printer-friendly version
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)















Comments
Manuel Jordan replied on Thu, 2009/11/19 - 10:25pm
I hope see a better documentation about EHCache
and furthermore see this Quartz support in Terracotta book second edition
Alex Miller replied on Fri, 2009/11/20 - 9:55am
in response to: dr_pompeii
dzoneCody replied on Fri, 2009/11/20 - 9:59am
"What else do you think would be a good fit for the Terracotta umbrella? "
Maybe a super-speedy web server to frontend the Terracotta clusters?
ARI ZILKA replied on Fri, 2009/11/20 - 10:27am
in response to: dzoneCody
Jim Bethancourt replied on Fri, 2009/11/20 - 11:44am
I realize this wouldn't be an "acquisition", but I think it could remove barriers to folks deploying Terracotta, similar to the way you've done with other clustered Terracotta products.
Cheers, Jim
OOO CCC replied on Fri, 2009/11/20 - 1:14pm
Henk De Boer replied on Sun, 2009/11/22 - 12:02pm
This is probably not the right place to ask, but I hope Terracotta finally fixes a small annoyance with Quartz that has been there for a long time: update the .xsd for the XML job file. Quartz 1.6.x still comes with the 1.5 version (http://www.opensymphony.com/quartz/xml/job_scheduling_data_1_5.xsd), but the format has actually changed in 1.6.
This causes a number of XML validation errors, which looks very unprofessional.
I think more than one topic has been opened for this already a various posters have provided patches for the 1.5 xsd already.
Manuel Jordan replied on Mon, 2009/11/23 - 9:27am
in response to: puredanger
Hello Alex
I mean for example include functional sample code in the distribution release to let us do own our experiments, in the documentation page I see many snippet code and few part about the explanation of the reason of the things, and some links broken
Regards
-Manuel