How do you design complex Rails systems?

We have the following systems (and more) that we push / retrieve data from one application to another:

  • CRM Hosting (InsideSales.com)
  • Asterisk Telephone System (Internal)
  • Banner ad system (openx, we host)
  • Lead Generation System (Homegrown)
  • E-commerce store (spree, we host)
  • Task board (homegrown)
  • Number of failures at the workplace + incoming tasks
  • Email delivery system (e.g. Mailchimp, homegrown)
  • Event management system (e.g. eventbrite, homegrown)
  • Dashboard system (lots of charts and reports that extract information from all other systems).

With Rails 3 around the corner, I really want to pursue a micro-application strategy, but I'm trying to decide whether to speak applications through the REST HTTP API or because I control them all, should I do something like general models in code that simplifies. but also allows material to flow across borders much easier ...

I heard that 37signals have a lot of small applications, I'm curious how these applications communicate with each other ... Or if you have any tips from your own experience with multiple applications.

Thank! I tried asking for it on my blog http://rywalker.com/chaos-2010 some time ago.

+5
source share
4

- , REST API.

: /, .

, , .

+4

DHH...

, REST. , , - 37- . . REST . , , .

+5

: , HTTP. : REST API XML/JSON memcache . ( , memcache , memcache )

API KEY HTTP .

+3

- AMQP ( rabbitmq ).

0

All Articles