4 ms·
DB: Postgres API: Ruby on Rails Frontend: React, the react_on_rails gem to set up webpack, Flow, Redux, Immutable.js Background Jobs: Sidekiq and Redis Cach
by nathan_f77 9y ago
DB: Postgres
API: Ruby on Rails
Frontend: React, the react_on_rails gem to set up webpack, Flow, Redux, Immutable.js
Background Jobs: Sidekiq and Redis
Caching: Memcached
PaaS: convox (on AWS). See: https://convox.com https://convox.com and https://github.com/convox/rack https://github.com/convox/rack (But you should start with Heroku.)
I recommend the Rails stack. It's not the "hot new thing", but it's very stable, secure, and productive.
- setquk 9y agoDefinitely agree with memcached. This has been entirely bullet proof for us for years. We have had lots of nodes with billions of hits each running non stop for 3 years without a reboot on CentOS 5. Zero maintenance required. Amazing bit of software.
- Tobani 9y agoWhile memcached is great. I feel like its hard to argue for both redis AND memcached. It seems like redundant infrastructure unless you have very specific needs.
- setquk 9y agoYes I agree there. I would err towards redis these days myself as well, not necessarily using it for anything persistent unless you need to.
- nathan_f77 9y agoIt's not a good idea to use a single Redis instance for both caching and persisted/transactional data (background jobs). For background jobs, you need real-time persistence with AOF. For caching, you want everything in memory, and you need an LRU cache that evicts any old data. This means you should run two Redis instances with different configurations. But in that case, it can be a good idea to use Memcached, which is recommended by Mike Perham [1]. [1] http://www.mikeperham.com/2015/09/24/storing-data-with-redis/ http://www.mikeperham.com/2015/09/24/storing-data-with-redis...
- bauerd 9y agoMy favorite stack as well, minus Convox (haven't heard of it before though). A no-brainer for me personally, unless there are realtime requirements.