Geek Answers Handbook

Crashing a Rails application internally through an API. a good idea?

I came across a great Rails application here. This company has a regular network, smartphone version, iphone, android version of the service. Android and Iphone use a very limited API.

They use the old version of Rails, and the code is generally not good to look at. I would like to somehow break this big ball of complexity to make it more accessible and updated in the future.

So, I thought it would be possible to create an API over controllers and models. Web applications and phones are allowed to use only this API.

Thus, the API will run on different servers, and each time we can focus on each component. We can also customize our API specifications once for all services.

My main concerns:

  • Would it take too long to prototype this system?
  • Is the access we need to the underlying data too complicated?
  • performance
  • Servers with APIs will need controllers and models, will there be duplicate controllers also at the ends of the web interface?

In the document, everything looks very good. Does anyone have experience creating something like this?

By the way, this looks very useful https://github.com/nesquena/rabl

+4
source share
1 answer

read the book, service oriented design with ruby ​​and rails

+1
source

More articles:


All Articles