Hi Adrian,
I've been discovered :) I enjoyed exploring a ESB scenario. In abstract you
may go along the lines of any of ESB solutions this way:
1) Any task is performed by suitably configured components
2) componets live in a container
3) components communicate through a message router
4)
Hi Luca
Thanks for the links!
I definitely have a lot of hammock time ahead of me :-)
Cheers
Adrian
On 11 Feb 2014, at 14:37, icamts wrote:
Hi Adrian,
the answer is more off-topic than the question :) but have a look to Spagic
(I'm a member of the developers' team), Mule ESB, Petals ESB
Hi Adrian,
the answer is more off-topic than the question :) but have a look to Spagic
(I'm a member of the developers' team), Mule ESB, Petals ESB or Talend ESB.
You may already know Talend as an ETL solution. You'll find tools to
define, configure and run instances of services or processes.
Hi Everyone,
This is a wee bit off topic, but given the sorts of problems the Clojure
community likes to solve and the enterprise background of a lot of people I
thought this list might be a good place to start.
We are building a fairly large web-infrastructure running over a
combination of
Considering your enterprise/cloud requirements, it seems that quartz
(http://clojurequartz.info/) http://clojurequartz.info/ should be the
closest to your needs. It's also integrated into Immutant
(http://immutant.org/tutorials/jobs/) http://immutant.org/tutorials/jobs/.
More generally in the
Perhaps I should be more precise: quartz (http://quartz-scheduler.org/)
http://quartz-scheduler.org/ is a java-based open source scheduler,
and the link I gave earlier is to the clojure integration layer
quartzite (http://clojurequartz.info/) http://clojurequartz.info/.
Immutant
fmj...@gmail.com writes:
Perhaps I should be more precise: quartz (http://quartz-scheduler.org/)
http://quartz-scheduler.org/ is a java-based open source scheduler,
and the link I gave earlier is to the clojure integration layer
quartzite (http://clojurequartz.info/)
On 10/02/14 16:20, Toby Crawley wrote:
Actually, Immutant has its own Quartz integration, and is not based on
quartz-clj. You can, however, use the Quartzite API with the
cluster-aware Quartz scheduler that Immutant provides if you prefer
the Quartzite API over the Immutant one. - Toby
Thanks
Hi François
Thanks for the info. Quartz and it's Clojure DSLs seem to do some of what I
need. I had a quick scan of the docs and they don't appear to support triggers
that are not time based (on arrival of a file, on completion of a job etc) -
but it was only a quick scan so I wondered if
Hi François
I totally agree about the scheduling library being only part of the solution.
I'm aware of Pallet but I have never used it in anger. The links you have
provided look like an interesting angle. I'll start working through them and
see if I can figure out an architecture that meets
On 10/02/14 18:46, Adrian Mowat wrote:
Thanks for the info. Quartz and it's Clojure DSLs seem to do some of
what I need. I had a quick scan of the docs and they don't appear to
support triggers that are not time based (on arrival of a file, on
completion of a job etc) - but it was only a
While not specifically a scheduling tool, Clara is a forward chaining rule
engine that can be used to implement a FSM and/or controller logic. I would
imagine you would want to layer this on top of a library like Pallet,
Quartz or Storm. Clara's Storm support is useful for distributed
12 matches
Mail list logo
