[erlang-questions] Re IOS/Android && OMADF && Erlang/JMS tapping into order data stream ..

Jorgen Skogstad <>
Fri Feb 21 03:11:38 CET 2014


Apologies if this is trivial for most of you - known about Erlang for a
long time, but not gotten my hands dirty with hands on yet.. but that's
about to change now I reckon. ;-)

Was wondering whether there were anyone that have done something similar to
what I am conceptualizing. Essentially want to take Oracle AIA order
streams, and tapping into that data through AIA sensors, which passes order
messages through to a foreign JMS provider. Was pondering then having
Erlang on the receiving end processing that data in a parallel spawn() like
manner given the transient nature of in-bound order data (e.g. process in
real time as the order messages are committed), and managing that
in-memory, with persistence ... building essentially the data/table
structure that I want synchronized through to the mobile application. Hence
for this section of the architecture - anyone had any luck doing something
like that?

Then, once that is done, was wondering whether I could use Erlang on
IOS/Android to syncronize the data (automatically) when the device is
online. That could be a bit of a challenge given the dynamic IP nature of
the device I suspect, but perhaps dynDNS could help, but not thought that
through. If that is too complex, then building a device sync service that
pulls data from serverside mnesia/couchdb could be another avenue..

.. then likely be the approach of building a Oracle Mobile ADF application,
that uses the local sync using something like the strategies outlined here:


Guess that means that I could expose the Erland mnesia/couch as RESTful
services through yaws, and then sync/update the local sqlLite db at times.

Really no specific reason for why OMADF, but where I work we have that for
$0, and this would just allow for a very simple and rapid concept cycle
across IOS & Android.

Any thoughts?

With respect,
Jørgen Skogstad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140221/80bc5bd5/attachment.html>

More information about the erlang-questions mailing list