From this:
http://www.rabbitmq.com/blog/2012/04/25/rabbitmq-performance-measurements-part-2/
The slowest scenario, persistent messages (for guaranteed delivery
scenarios) RabbitMQ can get more then 4000 msg/sec. Remember those stuff
are designed for massive scalability.
Compared to direct HTTP calls, in most cases it would provide a way
faster experience since most operations could be done async.
For example, imagine a scenario where you need to create/update a
product with Magento. By using directly the synchronous HTTP API, you
would POST, wait for Magento to process the request and await a 200 OK
response. Depending on the latency it could block user interaction for a
long time. Additionally, if the Magento service is for any reason
unreachable, the user will see an exception.
Using a message queue, you could asynchronously send the message to a
queue, require message persistence for guaranteed delivery and forget
about it. When it's ready, Magento (probably an "adapter") could pick
the message and process the product creation request.
The drawback is that for a brief moment, you lose synchronization -
you've got a new product on OpenERP and no product in Magento. But in
most cases, one can live with that.
The other major advantage, is that you decouple both systems. OpenERP
need not to know about Magento. All it need to know is that it must post
a message in a canonical data model (probably very close to OpenERP data
model) to given queue when it create/update a product. The receiving
part (usually a thin adapter) need not to know about OpenERP, only that
when a message arrives in a given queue, it need to process the message.
If you ever decide to change Magento to Prestashop or Spree, no change
to OpenERP is necessary, you just have to change the thin adapter.
BTW, I'm using ActiveMQ (JMS+Stomp) to integrate OpenERP, our legacy
manufacturing system and POS'es which are geographically dispersed on
crappy ADSL connections.
Em 14/12/2012 21:53, Maxime Chambreuil escreveu:
Hello,
I have heard at the last community days that API could be fairly slow (Magento
was given as an example). So I am not sure adding other layers/tools/software
would make such connection a viable solution for real life systems.
We haven't tested API performance of SugarCRM and Redmine yet (RT doesn't have
one AFAIK).
I would be willing to know if there is anyone using this kind of solution with
OpenERP and their feedback of using it. We've been using direct connection so
far and customers seem to like it.
Have a great week-end!
_______________________________________________
Mailing list: https://launchpad.net/~openerp-expert-framework
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-expert-framework
More help : https://help.launchpad.net/ListHelp
