Building the Future of On-Call: Why Velocity Moved from RDS to Neon
Blog post from Neon
Velocity, a fast-moving startup, switched from AWS RDS to Neon for their database solution due to easier scalability across clouds, allowing them to scale effortlessly without managing separate configurations per cloud. This switch also provided faster development workflows through Neon's branching model, which enabled developers to instantly create branches and test schema changes safely. Additionally, Velocity gained reliable support when it mattered most, with immediate access to real support engineers. They are now experimenting with pgvector for embeddings and leveraging observability features to diagnose issues quickly.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Vector Search | 6 | 2,390 | 404 | 144 | +11% |
| Observability | 2 | 2,514 | 532 | 153 | +20% |
| Real-time | 2 | 7,559 | 1,298 | 252 | +46% |
| AI Agents | 1 | 2,521 | 463 | 157 | -2% |
| Serverless | 1 | 1,628 | 326 | 111 | +97% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.