In part, this is because oldsters appreciate its steady reliability. That said, neither MySQL nor Oracle are going to lose their places as the Top 2 most popular database technologies in the world anytime soon, to PostgreSQL or anything else. OpsCompass CTO John Grange indicates that his clients prefer PostgreSQL in significant part because it’s not Oracle. Why? Because MySQL has one primary contributor: Oracle. This last point is telling, because it’s very possible that over time PostgreSQL will displace MySQL. It’s a true, vendor-neutral open source community. The documentation is wonderful, the data types reflect the types developers work with, and there is little surprising.” Unlike every other Top 10 database, PostgreSQL doesn’t depend on any single vendor. Not only that but, as Elijah Zupancic, Joyent’s director of solutions engineering, put it to me, PostgreSQL also gets developer essentials right: “From a developer perspective, it is a pleasure to use. In fact, when I asked why PostgreSQL is experiencing such a renaissance, most respondents focused on the impressive (if boring) aspects of the database: its focus first on data integrity and correctness, ability to extend the database through runtime extension hooks, and the opportunity to query other systems within PostgreSQL through foreign data wrappers. Making the boring things boringīeyond this newfangled scale and NoSQL-y functionality, PostgreSQL has always done the essentials of a database well. With Citus, scale comes natively to PostgreSQL. In this way, as Craig Kerstiens, Citus’s head of cloud, says, SaaS startups or established enterprises that start with PostgreSQL can do so without worrying that they’ll later need to rearchitect for NoSQL to get scale. The company behind Citus provides commercial tools (as well as a fully managed Citus database), but the tools simply make it easier to manage the scaling. With Citus, an open source extension to PostgreSQL, it’s now easy to scale out PostgreSQL across multiple nodes and intelligently distribute transactions and SQL queries to get massive parallelism, as well as a much bigger compute, memory, and disk footprint for the database. As Google, Facebook, and others have shown, real scale is horizontal-and PostgreSQL was hamstrung there. ![]() Sure, you could mortgage a residential neighborhood’s homes and get Oracle’s entry-level vertical scale, but that’s not how the world works anymore. One thing that PostgreSQL (and RDBMS, generally) hasn’t done well is scale. ![]() ![]() Originally it wasn’t very good, but by Version 9.4 JSONB gave the venerable database significant mojo (and heavy-duty indexing).Īlso, as Redmonk analyst James Governor has pointed out, “there’s some NoSQL and big data fatigue,” so suddenly developers stuck with their tried-and-true PostgreSQL as a viable alternative to MongoDB and Apache Cassandra for some key workloads. Arguably, one of the biggest innovations to hit PostgreSQL in years made it look a bit less frumpy: native JSON support in PostgreSQL 9.2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |