There was a similar talk[1] at FOSDEM, where the speaker describes how, as an experiment, he replaces a full ELK stack plus other monitoring tools with PostgreSQL. He even goes as far as implementing a minimal logstash equivalent (i.e. log parsing) into the database itself.
It wasn't an "we do this at scale" talk, but I'd love to see more experiments like it.
For the impatient: Skip to 17 minutes into the video, where he describes the previous architecture and what parts are replaced with Postgres.
There's for example Aiven, which is offering managed Postgres in cloud [1]. They also have similar managed offerings for various other open source tools. They raised $40M earlier this year.
Oooh, making it a standardized postgres extension (rather than its own compiled fork) is suuuuper-compelling. I've toyed with pipelinedb here and there, but the mental overhead of maintaining it separately from postgres is a little heavy. Even if the benefit is largely psychological, I think this is a great move.
Would love to see this! I could see a wasm version of postgres being useful for all sorts of things, especially an easy dev instance of pg runing inside a node app.
Or managed Postgres on AWS Aurora, AWS RDS, Google Cloud SQL, Heroku, etc :)
SNS, Kenesis (Kafka), Google Pub/Sub are awesome. Not the same problem/solution fit as an event store, but awesome for the scenarios and architectures they're targeted at.
That's how I've been thinking/talking about it. It should be a drop-in replacement for Postgres. Obviously the install process isn't as smooth yet, but, technical preview...
It wasn't an "we do this at scale" talk, but I'd love to see more experiments like it.
For the impatient: Skip to 17 minutes into the video, where he describes the previous architecture and what parts are replaced with Postgres.
1. https://fosdem.org/2017/schedule/event/postgresql_infrastruc...
reply