Relational Databases Resources

Looking for input from G2 reviewers who are software engineers, backend developers, and full-stack developers in the Relational Databases category, specifically from those who have implemented a relational database as the primary data store for a production application.

The platforms with the strongest software engineer production reliability evidence:

• PostgreSQL: The WAL-based crash recovery model is specifically credited for producing databases that recover to a consistent state after unexpected shutdowns rather than requiring manual repair or data loss assessment.
• MySQL: The depth of operational knowledge available from the community, the hosting ecosystem, and the breadth of managed services built around MySQL means that production issues are reliably diagnosable and recoverable without specialised database expertise.
• Microsoft SQL Server: The comprehensive SQL Server Agent for scheduled job management and the built-in monitoring through SQL Server Management Studio are credited for giving software engineers the production observability they need to identify issues before they become failures.
• Amazon RDS: The automatic minor version patching and security updates remove the maintenance burden that software engineers running self-managed databases must schedule around active application traffic.
• SQLite: Software engineers credit the simplicity of the reliability model for embedded and edge applications where the absence of a separate database process to monitor and restart is the reliability advantage over server-based alternatives.

For software engineers who have operated a relational database in production for more than one year: what was the first production incident that was caused by database behaviour rather than application code, and was the root cause a schema design decision, a missing index, a configuration default, or a platform-specific behaviour you had not encountered in development?

Looking for input from G2 reviewers who are software engineers, backend developers, and full-stack developers in the Relational Databases category, specifically from those who have implemented a relational database as the primary data store for a production application.

The platforms with the strongest software engineer production reliability evidence:

• PostgreSQL: The WAL-based crash recovery model is specifically credited for producing databases that recover to a consistent state after unexpected shutdowns rather than requiring manual repair or data loss assessment.
• MySQL: The depth of operational knowledge available from the community, the hosting ecosystem, and the breadth of managed services built around MySQL means that production issues are reliably diagnosable and recoverable without specialised database expertise.
• Microsoft SQL Server: The comprehensive SQL Server Agent for scheduled job management and the built-in monitoring through SQL Server Management Studio are credited for giving software engineers the production observability they need to identify issues before they become failures.
• Amazon RDS: The automatic minor version patching and security updates remove the maintenance burden that software engineers running self-managed databases must schedule around active application traffic.
• SQLite: Software engineers credit the simplicity of the reliability model for embedded and edge applications where the absence of a separate database process to monitor and restart is the reliability advantage over server-based alternatives.

For software engineers who have operated a relational database in production for more than one year: what was the first production incident that was caused by database behaviour rather than application code, and was the root cause a schema design decision, a missing index, a configuration default, or a platform-specific behaviour you had not encountered in development?

Looking for input from G2 reviewers at software companies, SaaS teams, and IT services organisations in the Relational Databases category, specifically from those who have selected a relational database as the foundation for a production application and can speak to which platform held up as the codebase grew.

The platforms with the strongest software and IT company evidence:

• PostgreSQL: The combination of SQL standards compliance, performance under complex workloads, and extensibility that allows teams to add capabilities through extensions rather than changing databases is described as the architecture choice that ages well as a software product grows.
• MySQL: Software teams building standard CRUD applications, content management systems, and e-commerce backends credit the predictability and tooling ecosystem for keeping development velocity high without specialised database expertise.
• Microsoft SQL Server: The SQL Server Management Studio tooling, the reporting and analytics integration with the Microsoft BI stack, and the compatibility with .NET application frameworks are credited for making development and database administration accessible without requiring specialised DBA expertise.
• Amazon RDS: The ability to run MySQL, PostgreSQL, or SQL Server on RDS while AWS handles the operational overhead is credited for allowing small software teams to operate production databases without a dedicated database engineer.
• SQLite: Software teams building mobile applications, desktop applications, and lightweight backend services credit SQLite for the development simplicity that eliminates the local database server setup step before coding can begin.

For software engineers who have chosen a relational database for a project that has now been in production for more than two years: what was the database-level behaviour that surprised you most as the data volume grew beyond what the initial design anticipated, and was the response a schema change, an indexing strategy, or a decision to evaluate a different database?