3 ms·
My preference at this point is rail's in api mode with a separate javascript fronted. I haven't had had to scale enough to really see it, but I often see render
by technion 4y ago
My preference at this point is rail's in api mode with a separate javascript fronted. I haven't had had to scale enough to really see it, but I often see rendering discussed as CPU heavy and I do wonder how much it helps that all my rendering is the OJ gem.
- aantix 4y agoWith proper nested catching, you can see response times in 50ms. No need to over complicate the views with a separate js front end.
- xoac 4y agoIf you go this route you end up having a drastically more complicated front end, and usually without the speed benefit. Unless you really need a SPA I would stay away.