Which RDBMS do you feel best suits the needs of today's climate of rapid change and iteration?
SQLite10%
CouchDB12%
PostgreSQL23%
MongoDB33%
SQLServer19%
1486 PARTICIPANTS
CTO in Software, 11 - 50 employees
Snowflake CTO in Finance (non-banking), 11 - 50 employees
CouchDB and Mongo are not RDBMS but at Document-oriented databases. SQLLite has relational features but calling it a full RDBMS is a stretch.Sr. Enterprise Technology Strategist in Software, 1,001 - 5,000 employees
Snowflake or a similar data “engine” as part of a broader data platform that can manage relational, object, graph and stream/telemetry types of data.Executive Architect in Healthcare and Biotech, 10,001+ employees
Oracle Autonomous Database. It is a multimodel converged database incorporating machine learning-based automation.VP of IT in Software, 51 - 200 employees
We use MongoDb and are perfectly happy with it. has more important fearures compared to SQLliteCIO in Services (non-Government), 201 - 500 employees
As previously noted, Mongo isn’t really an rdbms. However, it has come a long way in supporting flexible schemas and performant relational functionality. We initially adopted it for iterative development of an in-house statistical data dashboard and are currently working on a refactor of that. When looking at alternative traditional rdbms’ or lightweight versions like SQLite, ultimately we found that latest iterations of Mongo support the level of relational separation and transactional modeling we wanted while still offering the flexibility of optimized document store. It’s definitely a contender at small scale, but I’m guessing based on the percent of people who chose it as a “preferred rdbms” here that our experience scales pretty far up, even if not all the way to F5000 size. At those scales though there is rarely less than some mix of data store engines in use with multiple teams (and in at least one client’s case multiple divisions) dedicated just to ETL to glue legacy and new services together across the mix of platforms. P.S. Snowflake comes up a lot too.Chief Technology Officer and Chief Information Officer, Self-employed
I had trouble pointing one database. Some are relational, some are document databases. It's like comparing a hammer and a screwdriver, which is better? When comparing databases agnostically of the purpose, then I'd choose security, performance, scalability, and availability as the main parameters.Director & Head of Engineering in Software, 51 - 200 employees
I think DB's planet scale can offer a different view on RDBMS usage.Chief Information Technology Officer in Finance (non-banking), 51 - 200 employees
SQLServer carries over a considerable number of legacy apps and code on it, but many of the others are more suitable for RD. Surprised not seeing mySQL on the list... Director of IT in Education, 10,001+ employees
MongoDBContent you might like
Limited understanding of benefits18%
Organizational silos61%
Unclear communication53%
Employee skepticism55%
Resistance to existing workflows16%
Unclear roles20%
Job security concerns4%
51 PARTICIPANTS
CTO in Software, 201 - 500 employees
Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.Coaching and mentoring10%
Facilitating/scaling Agile47%
Removing impediments22%
Owning best practices10%
Leading Scrum meetings4%
Tracking progress2%
Sharing Agile knowledge across the org2%
I’m not sure2%
Something else not listed here0%
96 PARTICIPANTS
Director of IT in Education, 10,001+ employees
Learning, Pseudocode, Code completion, quick answers