Ruby On Rails Laitkor |
1. For the developer who has scaled multiple Rails sites, a millions or more of PV / month, the runtime performance of the interpreter is never the slowest. Scaling a site is more interesting as about architecture, caching. Queues, event, databases, disc IO, CDNs, etc. The runtime or framework doesn’t crack the top 5 except only a few of them.
2. One of the most important of all, Rails is the most efficient framework right now to build your app quickly and effectively. So you need to stop worrying so much and start building it.
4. The appropriate phrase for this could be “good developers are able to make systems more scalable while bad developers will always make non-scalable systems”. The answer is “yes, Rails do try to facilitate scalability.” It tries for a shared-nothing architecture. There are several; known techniques if you really need to add more hardware or more layers, such as having load balancers, caching servers, etc.
6. You need to use the right tool for the right job. You are not required to use a highly abstracted language for a high- traffic queuing backend, use it to make features.
A Rails app should have ‘flat controllers’ with as little code as possible. These controllers will refer to services which retrieve data. As time goes on, you may begin to pull these services out of the application itself and into their own processes. For any further assistance, switch to Laitkor and get all your queries answered by our expert members.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.