fernandomxQ: MySQL vs PostgreSQL and performance (>1,000,000 rows)
Hello,
I am interested in plan 5 but I am curious to know: Why did you choose MySQL and not PostgreSQL? pgsql has been the #1 most used/recommended option in recent years in most surveys conducted (this includes SAAS), and although MySQL/MariaDB is also widely used, that is mainly due to CMS systems like WordPress. pgsql has native row-level security (RLS) built in, and from what I read, you had to develop that abstraction layer for MySQL.
I was also struck by the consideration for table size being 1,000,000 records, which seems very low to me (to think there might be a performance issue), and this worries me since in 1-2 years I might easily have at least one table that reaches that number of records. Has this changed/improved over time?
Is it possible to create triggers, stored procedures, and jobs?
Riya_NoCodeBackend
Apr 3, 2026A: Hello,
Great questions — really appreciate the thoughtful comparison.
We chose MySQL for its operational simplicity, predictable performance, and ease of managing multi-tenant workloads at scale. While PostgreSQL offers native features like RLS, we’ve built our own access control layer tailored for “vibe-built” apps created via tools like Cursor and Visual Studio Code, keeping things simple and developer-friendly without requiring deep database expertise.
On the 1,000,000 rows point — that’s not a hard limit. It’s a conservative guideline for optimal performance. With proper indexing and usage patterns, handling significantly larger datasets is absolutely possible and something we’ve been improving continuously.
Currently, we don’t support triggers, stored procedures, or jobs. NCB is built as an automatic backend for vibe-coded apps (built using tools like Cursor or VS Code), focusing on simplicity and speed rather than traditional database complexity.