Is PostgreSQL good enough?
tldr; you can do jobs, queues, real time change feeds, time series, object store, document store, full text search with PostgreSQL. How to, pros/cons, rough performance and complexity levels are all discussed. Many sources and relevant documentation is linked to.
Your database is first. But can PostgreSQL be second?
Web/app projects these days often have many distributed parts. It's not uncommon for groups to use the right tool for the job. The right tools are often something like the choice below.
Redis for queuing, and caching.Elastic Search for searching, and log stash.Influxdb or RRD for timeseries.S3 for an object store.PostgreSQL for relational data with constraints, and validation via schemas.Celery for job queues.Kafka for a buffer of queues or stream processing.Exception logging with PostgreSQL (perhaps using Sentry)KDB for low latency analytics on your column oriented data.Mongo/ZODB for storing documents JSON (or mangodb for /dev/null replacement) SQLite for embedded. Ne…
Your database is first. But can PostgreSQL be second?
Web/app projects these days often have many distributed parts. It's not uncommon for groups to use the right tool for the job. The right tools are often something like the choice below.
Redis for queuing, and caching.Elastic Search for searching, and log stash.Influxdb or RRD for timeseries.S3 for an object store.PostgreSQL for relational data with constraints, and validation via schemas.Celery for job queues.Kafka for a buffer of queues or stream processing.Exception logging with PostgreSQL (perhaps using Sentry)KDB for low latency analytics on your column oriented data.Mongo/ZODB for storing documents JSON (or mangodb for /dev/null replacement) SQLite for embedded. Ne…
Comments