Join Percona Chief Evangelist Colin Charles as he covers happenings, gives pointers and provides musings on the open source database community.
This is a short working week for me due to a family emergency. It caused me to skip speaking at DataOps.Barcelona and miss hanging out with the awesome of speakers and attendees. This is the first time I’ve missed a scheduled talk, and I received many messages about my absence. I am sure we will all meet again soon.
One of the talks I was planning to give at DataOps.Barcelona will be available as a Percona webinar next week: Securing Your Database Servers from External Attacks on Thursday, June 28, 2018, at 7:00 AM PDT (UTC-7) / 10:00 AM EDT (UTC-4). I am also giving a MariaDB 10.3 overview on Tuesday, June 26, 2018, at 7:00 AM PDT (UTC-7) / 10:00 AM EDT (UTC-4). I will “virtually” see you there.
If you haven’t already read Werner Vogel’s post A one size fits all database doesn’t fit anyone, I highly recommend it. It is true there is no “one size fits all” solution when it comes to databases. This is why Percona has made “the polyglot world” a theme. It’s why Amazon offers different database flavors: relational (Aurora for MySQL/PostgreSQL, RDS for MySQL/PostgreSQL/MariaDB Server), key-value (DynamoDB), document (DynamoDB), graph (Neptune), in-memory (ElastiCache for Redis & Memcached), search (Elasticsearch service). The article has a plethora of use cases, from AirBnB using Aurora, to Snapchat Stories and Tinder using DynamoDB, to Thomson Reuters using Neptune, down to McDonald’s using ElastiCache and Expedia using Elasticsearch. This kind of detail, and customer use case, is great.
There are plenty more stories and anecdotes in the post, and it validates why Percona is focused not just on MySQL, but also MariaDB, MongoDB, PostgreSQL and polyglot solutions. From a MySQL lens, it’s also worth noting that not one storage engine fits every use case. Facebook famously migrated a lot of their workload from InnoDB to MyRocks, and it is exciting to see Mark Callaghan stating that there are already three big workloads on MyRocks in production, with another two coming soon.
Releases
- MariaDB 10.1.34 – including fixes for InnoDB defragmentation and full text search (MDEV-15824). This was from the WebScaleSQL tree, ported by KakaoTalk to MariaDB Server.
- Percona XtraDB Cluster 5.6.40-26.25 – now with Percona Server for MySQL 5.6.40, including a new variable to configure rolling schema upgrade (RSU) wait for active commit connection timeouts.
- Are you using the MariaDB Connector/C, Connector/J or Connector/ODBC? A slew of updates abound.
Link List
- LemonGraph is a log-based transactional graph (nodes/edges/properties) database engine that is backed by a single file. It inherits from Symas LMDB. Maybe the most interesting aspect of this software is that it comes out from the National Security Agency (NSA).
- Xmysql allows you to generate rest APIs for any MySQL database.
- JetBrains State of the Developer Ecosystem 2018: Databases tells you that MySQL, PostgreSQL, and MongoDB are the top three regularly used databases. Adoption in the next 12 months suggests MongoDB, Redis and PostgreSQL as the top three. I find it interesting that the top three tools to access the database seems to be MySQL Workbench, the command line and then phpMyAdmin.
- Gracefully Scaling to 10k PostgreSQL Connections for $35/mo, Part One and Gracefully Scaling to 10k PostgreSQL Connections for $35/mo, Part Two are good reads.
- MySQL High Availability at GitHub – such a great read by Shlomi Noach, from GitHub’s High Availability objectives. It talks about how they weren’t afraid to move away from virtual IPs and DNS-based discovery, and how they have settled on Orchestrator, Consul and the Github Load Balancer/HAproxy. They do run GLB on top of HAproxy, and there was also a contribution to make pt-heartbeat better.
Industry Updates
- Nginx raised $43 million in Series C funding, led by Goldman Sachs Growth Equity. Total raised is now $103 million.
Upcoming appearances
- OSCON – Portland, Oregon, USA – July 16-19 2018
Feedback
I look forward to feedback/tips via e-mail at [email protected] or on Twitter @bytebot.