Why MariaDB?

This document summarizes a talk given by Michael "Monty" Widenius about reasons to switch to MariaDB 10.0 from MySQL 5.5 or MariaDB 5.5. The talk addresses why MariaDB was created, features of MariaDB releases, benchmarks, the role of the MariaDB foundation, and reasons to switch. It provides information on the MariaDB foundation goals of developing and distributing MariaDB openly. It outlines many new features in MariaDB 10.0 including new storage engines, replication features, functionality, and improvements in areas like speed, optimization, and usability.

MySQL and MariaDB are becoming more divergent. Learn what is different from a high level. It is also a good idea to ensure that you use the correct database for the correct job.

Meet MariaDB 10.1 at the Bulgaria Web Summit, held in Sofia in February 2016. Learn all about MariaDB Server, and the new features like encryption, audit plugins, and more.

An introduction to MongoDB from an experienced MySQL user and developer. There are differences and we go thru the What/Why/Who/Where of MongoDB, the "similarities" to the MySQL world like storage engines, how replication is a little more interesting with built-in sharding and automatic failover, backups, monitoring, DBaaS, going to production and finding out more resources.

The document provides an overview of the Complete MariaDB Server Tutorial presentation. It introduces MariaDB and discusses what it is, its goals of being compatible with MySQL and having stable releases. It also covers MariaDB architecture, installation, utilities, and storage engines.

Some best practices about tuning Linux for your database workloads. The focus is not just on MySQL or MariaDB Server but also on understanding the OS from hardware/cloud, I/O, filesystems, memory, CPU, network, and resources.

This document summarizes a presentation on MariaDB/MySQL security essentials. The presentation covered historically insecure default configurations, privilege escalation vulnerabilities, access control best practices like limiting privileges to only what users need and removing unnecessary accounts. It also discussed authentication methods like SSL, PAM, Kerberos and audit plugins. Encryption at the table, tablespace and binary log level was explained as well. Preventing SQL injections and available security assessment tools were also mentioned.

MySQL is a unique adult (now 21 years old) in many ways. It supports plugins. It supports storage engines. It is also owned by Oracle, thus birthing two branches of the popular opensource database: Percona Server and MariaDB Server. It also once spawned a fork: Drizzle. Lately a consortium of web scale users (think a chunk of the top 10 sites out there) have spawned WebScaleSQL. You're a busy DBA having to maintain a mix of this. Or you're a CIO planning to choose one branch. How do you go about picking? Supporting multiple databases? Find out more in this talk. Also covered is a deep-dive into what feature differences exist between MySQL/Percona Server/MariaDB/WebScaleSQL, how distributions package the various databases differently. Within the hour, you'll be informed about the past, the present, and hopefully be knowledgeable enough to know what to pick in the future. Note, there will also be coverage of the various trees around WebScaleSQL, like the Facebook tree, the Alibaba tree as well as the Twitter tree.

This is my third iteration of the talk presented in Tokyo, Japan - first was at a keynote at rootconf.in in April 2016, then at the MySQL meetup in New York, and now for dbtechshowcase. The focus is on database failures of the past, and how modern MySQL / MariaDB Server technologies could have helped them avoid such failure. The focus is on backups and verification, replication and failover, and security and encryption.

Today you can use hosted MySQL/MariaDB/Percona Server in several "cloud providers" in what is considered using it as a service, a database as a service (DBaaS). You can also use hosted PostgreSQL and MongoDB thru various service providers. Learn the differences, the access methods, and the level of control you have for the various public cloud offerings: - Amazon RDS for MySQL and PostgreSQL - Google Cloud SQL - Rackspace OpenStack DBaaS - The likes of compose.io, MongoLab and Rackspace's offerings around MongoDB The administration tools and ideologies behind it are completely different, and you are in a "locked-down" environment. Some considerations include: * Different backup strategies * Planning for multiple data centres for availability * Where do you host your application? * How do you get the most performance out of the solution? * What does this all cost? Growth topics include: * How do you move from one DBaaS to another? * How do you move all this from DBaaS to your own hosted platform? Questions like this will be demystified in the talk. This talk will benefit experienced database administrators (DBAs) who now also have to deal with cloud deployments as well as application developers in startups that have to rely on "managed services" without the ability of a DBA.

Talking about the improvements in MariaDB on MySQL security and encryption features that are so important in today's data landscape. Presented http://www.meetup.com/EffectiveMySQL/events/224828891/

MySQL features missing in MariaDB Server. Here's an overview from the New York developer's Unconference in February 2018. This is primarily aimed at the developers, to decide what goes into MariaDB 10.4, as opposed to users. High level comparisons are made between MySQL 5.6/5.7 with of course MySQL 8.0 as well. Here's to ensuring MariaDB Server 10/310.4 has more "Drop-in" compatibility.

At the MariaDB Server Developer's meeting in Amsterdam, Oct 8 2016. This was the deck to talk about what MariaDB Server 10.1/10.2 might be missing from MySQL versions up to 5.7. The focus is on compatibility of MariaDB Server with MySQL.

This document summarizes a presentation given by Colin Charles on MariaDB. It introduces MariaDB as a community-developed, feature-enhanced, and backward compatible fork of MySQL. Key points covered include the origins and goals of MariaDB, its compatibility with MySQL, new features introduced in recent MariaDB versions like XtraDB and dynamic columns, and how the project aims to remain open source and community developed going forward.

Best practices for MySQL/MariaDB Server/Percona Server High Availability - presented at Percona Live Amsterdam 2016. The focus is on picking the right High Availability solution, discussing replication, handling failure (yes, you can achieve a quick automatic failover), proxies (there are plenty), HA in the cloud/geographical redundancy, sharding solutions, how newer versions of MySQL help you, and what to watch for next.

Having spent more than the last decade being the main point of contact for distributions shipping MySQL, then MariaDB Server, it's clear that working with distributions have many challenges. Licensing changes (when MySQL moved the client libraries from LGPL to GPL with a FOSS Exception), ABI changes, speed (or lack thereof) of distribution releases/freezes, supporting the software throughout the lifespan of the distribution, specific bugs due to platforms, and a lot more will be discussed in this talk. Let's not forget the politics. How do we decide "tiers" of importance for distributions? As a bonus, there will be a focus on how much effort it took to "replace" MySQL with MariaDB. Benefits: if you're making a distribution, this is the point of view of the upstream package makers. Why are distribution statistics important to us? Do we monitor your bugs system or do you have a better escalation to us? How do we test to make sure things are going well before release. This and more will be spoken about. As an upstream project (package), we love nothing more than being available everywhere. But time and energy goes into making this is so as there are quirks in every distribution.

MariaDB Server 10.3 is a culmination of features from MariaDB Server 10.2+10.1+10.0+5.5+5.3+5.2+5.1 as well as a base branch from MySQL 5.5 and backports from MySQL 5.6/5.7. It has many new features, like a GA-ready sharding engine (SPIDER), MyRocks, as well as some Oracle compatibility, system versioned tables and a whole lot more.

This document provides an overview and summary of various high availability (HA) solutions for MySQL databases. It begins with an introduction to HA and definitions of key terms. It then discusses MySQL replication, including asynchronous, semi-synchronous, and features in MySQL 5.6 and MariaDB 10.0. Other HA solutions covered include MHA for automated failover, Galera/MariaDB Galera Cluster for synchronous replication, shared disk solutions like DRBD, and MySQL Cluster for in-memory synchronous replication across nodes. The document provides brief descriptions of how each solution works and when it may be applicable.

This document compares MySQL and MariaDB, noting problems with MySQL like not being truly open source and limited features. It presents MariaDB as a drop-in replacement for MySQL that is open source and provides additional features like those in MySQL Enterprise. Examples are given of companies using MariaDB successfully at large scale like OLX, Wikipedia, and Tumblr. It concludes by offering a proof of concept to demonstrate MariaDB.

This document provides an introduction and overview of MariaDB. It highlights that MariaDB is a world class, secure and extensible open source database with the fastest growth. It is used by over 12 million users in 45 countries for critical business functions. MariaDB aims to radically simplify database adoption and supports various deployment options and use cases. It offers multiple storage engines and replication capabilities. World class support is available 24/7/365. The document promotes MariaDB's support, security, innovation and services.

The MariaDB update for 2011 from Michael Widenius of Monty Program. This was a keynote given on Wednesday 13 April 2011 at the O'Reilly MySQL Conference & Expo 2011.

This document provides an overview of some of the key changes and new features being introduced in CakePHP 2.0. Some of the major changes discussed include: refactoring the core codebase and removing unused code; upgrading to PHPUnit for unit testing; standardizing how objects inherit via new Component architecture; leveraging more of the Standard PHP Library; exceptions being used to indicate errors; centralizing request and response handling; and dropping support for PHP 4. New features highlighted include PDO database support, simplified URL rewriting, support for nested named parameters, and a refactored authentication system. The document also discusses some of the challenges faced, including retaining backwards compatibility while continuing to improve and modernize the framework.

El documento explica cómo SQLite puede usarse para organizar información en una aplicación de Unity3D. SQLite es una biblioteca de base de datos ligera que almacena todos los datos en un solo archivo, lo que la hace portátil. El documento guía al lector a través de la creación de una base de datos SQLite, la escritura de código para conectarse a ella y manipular datos, y probar el código en Unity3D y un navegador de bases de datos.

This document discusses using jQuery and CakePHP together for web development. It describes how jQuery can be used to simplify tasks like including JavaScript files and passing data from controllers to views. The author proposes using "jayDom", which involves encoding data in HTML microformats for semantic encoding and easy parsing between the browser and server via Ajax. Real-world examples are provided to illustrate accessing and updating microformat data with jQuery selectors. The goal is to more easily achieve "world domination" by building powerful applications with these techniques.