Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • hatchbox.io. Basically a Rails-focused service that sets up your AWS infrastructure for you, including postgres database, redis, Rails web and background workers (with horizontal-scaling and load-balancing). Also has a built-in system for distributing your config/env vars to all machines, like heroku.

    • You still have access to the underlying AWS, it just sets it up for you.

    • We’d still have to do Solr separatel, probably still with SearchStax.

    • Unclear how mature/complete it is, there are some things we’d need to do that it’s not clear to me how it would support, there would definitely be more manual hands-on than heroku, and probably require some custom solutions.

    • But it is much less expensive than heroku, $50-$100/month on top of the AWS resources you pay for yourself.

  • another new heroku-esque alternative I haven’t explored much: render.com

  • Stay on AWS, but with higher-level “managed” services.

  • Stay on current infrastructure BUT with more support from part-time/contract help

    • Look maybe in our library tech communities for person or vendor that could contract with us on a retainer or as-needed basis to help us do operations things as they come up

    • Might start with a larger project to help us re-design/re-architect our current setup to be based on more contemporary best-practices and be easier to manage

  • Some complicated docker/kubernetes based solution, using a hosted kubernetes platform.

    • This is very trendy right now, but I don’t know much about it. Ostensibly would take care of many operational concerns, but I suspect it would end up requirement more time investment than in utopian portrayals, beginning with investment to understand what it really is and how to set up our app for it.