4 ms·
Have you read this: http://s3.cleverelephant.ca/2017-cdb-postgis.pdf http://s3.cleverelephant.ca/2017-cdb-postgis.pdf
by bluedino 7y ago
Have you read this: http://s3.cleverelephant.ca/2017-cdb-postgis.pdf http://s3.cleverelephant.ca/2017-cdb-postgis.pdf
- durkie 7y agoYes -- it's a good talk, but it focuses mostly on tricks you can do (spatial indexing, geometry subdividing) on the PostGIS side to make lookups/calculations faster, but discussion of actually scaling to multiple databases is a bit light. There is mention of Citus (which Microsoft has purchased and rebranded as Hyperscale), but it has a minimum cost that is more than I can afford right now. I didn't know if there were other architectures to consider for rails -- like having a few read replicas for web traffic, and then a single large writable master for sidekiq/background jobs, for instance.
- jacobkg 7y agoRead replicas is a good way to go. Rails 6 has good built-in support for them: https://www.citusdata.com/blog/2019/05/23/rails-6-multiple-databases/ https://www.citusdata.com/blog/2019/05/23/rails-6-multiple-d...