Ruote 2.1 has a persisted workqueue. For the items placed in the queue, I use the term "message", it covers "tasks" (sent for execution by expressions) and "events" (intra-engine notifications).
An interesting consequence : a persisted workqueue can be shared by multiple workers, workers not in the same Ruby process.
A message ordering the launch of a ruote process looks like : {"type": "msgs", "_id": "1984-2151883888-1261900864.59903", …
- processi: it's barley a task manager
- Ruby News: Ruby 1.8.6 maintenance moved to Engine Yard
- ricroberts: Blink #1 - The first in a series of Link-Blogging posts
- Litany Against Fear: 5 Great Talks Notes
- Viget Extend : The Development Lab: Getting Started with MongoDB & MongoMapper
- Riding Rails - home: Community Highlights
…enterprise with ruby" is available as well as the presentation slides .
When the talk was over, it was good fun to go over to the two speakers and introduce myself. They explained to me what they liked about ruote and how they sold it to their team. Ruote seems to fit nicely in their services and DSLs. I hope to meet them again to learn more.
It was then time to attend the following talks of the kaigi. It was a great event, too much to cover.
- Open Sourcery: Driving Business Processes in Ruby
- Opscode Blog: Opscode Unveils Commercial Platform
- Headius: Announcing JRubyConf 2009
- RubyFlow - Search for jruby: RubyKaigi 2010 Conference Registration now open
- Luigi Montanez: Ten Ruby Conferences (and Three Camps) in Eight Weeks
- Ruby Inside: Padrino: A Webapp Framework Wrapped Around Sinatra
…that data has to be correlated, and I wanted to rethink how to do it. After plenty of discussions in # ruote with John Mettraux we came up with a model based on how the web works. Since CouchDB is "off the web", the approach feels quite fitting to me and hopefully to you too.
First some insight into my thinking at this stage.
The web has been successful in loosely expressing relationships between documents. Take two examples:
and
For those of you reading this through a …
- till's blog: PHP: So you'd like to migrate from MySQL to CouchDB? - Part II
- Litany Against Fear: 5 Great Talks Notes
- : jQueryConf 2009
- A Fresh Cup: Double Shot #562
- blog.webandy.com | Andy Atkinson: WindyCityRails 2008 conference
- English - AkitaOnRails.com: Rails Podcast Brasil, QCon Special - Nick Sieger (JRuby) and Francesco Cesarini (Erlang)
ruote 2.1.7 is out and it felt like it was time to update the CsvParticipant that could be found in ruote 0.9.
Ruote has been relying on rufus-decision for its decision table needs and ruote 0.9 was integrating a CsvParticipant directly. For ruote 2.1, the DecisionParticipant is left in the rufus-decision gem.
It's not the first time I write something about decision tables. But I noticed that I hadn't really written anything about how to mix ruote processes and decision tables.
- Junior developer: RubyForge email ham to spam rates
- Piotr Sarnacki: Tweaking Rails app with jQuery, part I
- Lindsay Holmwood - auxesis' musings: Thank you for the lies
- Momoro Machine: Ideas vs Features
- Khaled alHabache's official blog: StackOverflow cool Ruby questions 2
- Rail Spikes - Home: Let a human test your app, not (just) unit tests
…daemon, AMQP & XMPP bots as well as the newest addition, Ruote remote participants.
All this is fine and well, and people seem to like the project. The mailing list is getting some noise, we're over 200 watchers strong on Github and the IRC channel has some folks popping in to say hi.
However, daemon-kit quickly made me lazy and realize there is a couple of things it can do much better. If you've used a generator before, you'll notice the generated code …
- Rails on Edge: The Ruby Hoedown
- Luigi Montanez: Respect the Browser - Lessons from JSConf 2009
- Article RSS Feed: August 2009 Meeting
…Sinatra web application wrapping a ruote workflow engine. Ruote can run many process instances issued from different process definitions, but barley's processes are all instantiated from a single process definition.
The cursor expression does most of the work. It runs in sequence a ‘trace' participant and a ‘next' participant. Then if the field ‘next' is set in the workitem (most likely it has been chosen by the ‘current' participant), …
- processi: ruote and decision tables
- Daddy Fixes Everything: Elk M1 Security System Control with Perl Script
- braindump: Travel in the 21st century
- McKinney Station: Microapps Encourage Hacking
- MacRuby Posts: MacRuby 0.5 beta 2
- Ruby Best Practices: Solve the problem, not just a problem
Ruote 2.1 has a persisted workqueue. For the items placed in the queue, I use the term "message", it covers "tasks" (sent for execution by expressions) and "events" (intra-engine notifications).
An interesting consequence : a persisted workqueue can be shared by multiple workers, workers not in the same Ruby process.
A message ordering the launch of a ruote process looks like : {"type": "msgs", "_id": "1984-2151883888-1261900864.59903", …
- processi: it's barley a task manager
- Ruby News: Ruby 1.8.6 maintenance moved to Engine Yard
- ricroberts: Blink #1 - The first in a series of Link-Blogging posts
- Litany Against Fear: 5 Great Talks Notes
- Viget Extend : The Development Lab: Getting Started with MongoDB & MongoMapper
- Riding Rails - home: Community Highlights
…in Madrid, people have tremendously contributed to ruote 0.9 (many thanks guys !). Ruote 2.0 is a small jump from 0.9, literally a jump, not a step, explanations are required.
Then beer ensued . A ruedas y cervezas (rc2) is planned for next month, I wish I could attend. So if you're in Madrid and you're interested in ruote or, less narrowly, in Ruby / JRuby / Scala / Java, contact Nando Sola and join the abstra.cc and UPM guys for the rc2.