Sharing model definitions between Erlang and Rails (and mongodb) -
I have a rail app using mongodab through Mongodab and it is all right. The problem is ... I want to use Erring to do some background processing and I want to update the same Mongo / Mongomapper model with the results of this processing. What's the best way to share model definitions between two apps (Rail and Ehrling) and stay intelligible? It seems that if they are reaching the same record, trying to manage them separately would be problematic. If there is no "good" way, then am I sending it wrongly?
Additional information: It was good because I was originally doing background processing using Starling / Verling Client because I can use the same rail model and code. The performance was terrible, although I am looking for Irang to solve some of the efficiency problems. This large amount of data is being processed, but it can be easily processed in parallel.
I want to use ARLing as a meter intermediary through a relaxing or throttle interface.
P>
Edit: I wanted a little more light on this. Erling processing will need to know something about the model in advance. I'm basically using Ehrling to pull data from other places and fill out details of model objects. Therefore, for example, there may be a description field that I am scraping an XML file using xmerl_xpath: string ("// description / text ()"). I should be able to add methods that will work on model farms.
Mongodaibi two community-supported erolongs (Erlondo and Imongo). By reaching your Mangode through those drivers, you will get the original Erlang object.
Ruby -> Mongomper -> Mongo Rabbi Driver -> Mongodi -> (Imongo | Erlmongo) -> Erong
Comments
Post a Comment