Default to SQLite rather than Postgres and Redis

[mikestefanello]

When I started on this project, I wanted to make something that would get you up and running building a web app as fast and as easily as possible, providing you with practically everything you'd need. Including Postgres and Redis seemed like an easy choice but in reality, an overwhelming number of apps will not need (or want) these and there's nothing rapid about having heavy dependencies like that (plus needing to run docker, by default). It seems more logical to provide defaults that are faster, easier, and satisfy the greatest number of developers. If you happen to outgrow SQLite (and in-memory caches, etc), then upgrading to Postgres/Redis is very easy to do (and odds are if you're running at that scale you're not using a project like this one).

Current setup:

• Database: Postgres
  • https://github.com/jackc/pgx
• Cache: Redis
  • https://github.com/go-redis/redis
  • https://github.com/eko/gocache
• Tasks: Redis
  • https://github.com/go-redis/redis
  • https://github.com/hibiken/asynq
• Cron: Redis
  • https://github.com/go-redis/redis
  • https://github.com/hibiken/asynq

Proposed:

• Database: SQLite
  • https://github.com/mattn/go-sqlite3
• Cache: In-memory
  • https://github.com/maypok86/otter ?
  • https://github.com/eko/gocache w/ something in-memory (is this wrapper still worth using?)
• Tasks: SQLite
  • https://github.com/maragudk/goqite (I have some contributions that I feel are needed, but are quick)
• Cron: In-process
  • https://github.com/robfig/cron ? (is this worth even including)

[mikestefanello]

Work will be done in this branch: https://github.com/mikestefanello/pagoda/tree/lite

For the cache, we'll use

• https://github.com/maypok86/otter
• eko/gocache will be removed. It's a nice library but the less dependencies the better. Plus, it seems like the cache tag implementation for in-memory caching is flawed so I wrote my own.

[mikestefanello]

Done: #72