Hacker News new | past | comments | ask | show | jobs | submit login

I love postgres but it has some limitations:

- Want a KVstore? Do you know autovacuum? Do you know the connections pool limit? Do you want throughput or safety?

- Want a queue? is it sequential? Is it throttled? Is it fanout? Is it split by topic?

- Want a pubsub? do you care about more than once? do you care about losing messages? do you care about replaying messages?

- Want a lock? Do you know the connections pool limit (again)? Do you know about statement_timeout?

Yes, you can solve almost all issues listed above, but it's not that trivial.




Also: Will your implementation fall over if there's a long running transaction that stops vacuum from removing tuples?


this. it's like the only thing the market hasn't done yet is replace the nanny of my kids and make my wife jealous.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: