I’m a big fan of Neon postgres. It’s pretty much unbeatable value for the price. The documentation is good and multi-tech stack friendly and I created a repo in which I added all the awesome links about Neon Postgres - https://github.com/tyaga001/awesome-neon and wrote a tutorial https://www.freecodecamp.org/news/build-an-invoice-saas-app-...

What key features make Tau a compelling self-hosted PaaS alternative?

easy to deploy, built-in CI/CD, CDK and coming-up this month is spore-drive, a tool you can use to deploy and update tau on all your hosts with one command.

How does CopilotKit compare to other frameworks or tools for building AI assistants?

sounds like a great project. How do you handle performance with large message sizes?

IMO, think of it like switching from a bicycle to a car. The bicycle might be faster in certain conditions, but the car offers more features and flexibility for different terrains. Similarly, Neon’s database branching feature is like adding all-terrain capability.

I very much disagree with this. It is possible (and we do this in production) to branch a pg database without requiring these tools using `pg_dump` or `pg_dumpall` which uses the ability to branch a database. These can be integrated with either standard ORM tools or SQL scripts to achieve the same result with far better performance and lower cost. This very much appears to be a knowledge issue.

easy to slam others but I don't see what's bizarre about the article. It highlights a successful customer story where Neon (https://neon.tech) played a significant role in improving their db management with its db branching feature. Yes, caching and pooling helped, but Neon made their testing and development much faster and efficient and it's not easy to write such detailed articles. why not any constructive feedback which can help them?

fair point about the slower response times But Neon's not just any Postgres. They've got that whole serverless angle, which can be a game-changer for scaling and costs. Maybe the team's still figuring out how to optimize for that setup? Plus, with Neon, they probably ditched that whole SQLite-in-git headache.

Game changer for scaling and costs? It’s an 80 MB database that needs to get duplicated by n developers and a test and production instance. They could get away with a $200 beelink under a desk. I see no reason to prematurely scale. I would focus on making things fast and creating a “duplicate database” button so devs can work without interrupting prod

ohh wow but why switch away from PlanetScale though? and I think Supabase also serve a dedicated Postgres DB (that is powering the BaaS) and we can use Supabase just for database hosting as well.

yay i heard from someone in my network but I don't think they are serverless Postgres as IMHO "Postgres is all you need, even for vectors" checkout this post I found in a discord https://anyblockers.com/posts/postgres-is-all-you-need-even-...

nice to know but when you say "challenging real-world tasks" any use cases?

are you automating the end to end RAG pipeline?

That description is a little vague, so I need to improve that. The use cases we're focused on are ones with 1) dense unstructured text, like legal documents, financial reports, and academic papers; and 2) challenging queries that go beyond simple factoid question answering. Those kinds of use cases are where we see existing RAG systems struggle the most.