Excitement around so-called 'NoSQL' data systems is reaching feverish levels of hype, but how much is just fashion and how much really matters? Do we really need all of this new technology or could we do this with say, MySQL? Here we describe a globally deployed in-memory data system based on MySQL's NDB engine. Compared head to head, this system will match the performance of several popular NoSQL systems without sacrificing consistency or SQL support. We'll talk about what NoSQL is really good for and who really needs it - and why.
In this session, Sandro Mazziotta, Senior Product Manager, Data Services, HP Cloud Services will present a way to integrate and build on the OpenStack project, RedDwarf, to deploy public cloud managed data services. Sandro will review RedDwarf architecture, discuss RedDwarf challenges, and introduce a technical solution for data services operation, provisioning, and public cloud deployment of MySQL as a Cloud Database. He will also show how to leverage RedDwarf to launch other unstructured databases and big data / analytics services.
Want to know how Tweetdeck, Flipboard, and Gumi use MySQL in the cloud? Join the Amazon RDS team in this session and learn how to speed up your app development cycles. Studies show Database architects and engineers spend more than 40% of their app development time on installing, upgrading and managing low value database management tasks. In addition, they often have to wrestle with IT for compute and storage resources to scale the database to meet the fast growing needs of internet apps. Amazon RDS delivers MySQL as a fully managed service that is easy to use, operate and scale.
Having application properly instrumented allows to eliminate guesswork from understanding what is causing performance problem in given instance. "It is database because it is always database" logic may work for you many times until it finally does not.
In this presentation we will look into a ways to instrument application so it offers you right information helping both to understand your current performance and causes of performance issues. We will also look into how you can store and process instrumentation information to focus
MySQL is no longer merely the M in LAMP, but the centre of IT solutions that go far beyond being The Online Database. Today, MySQL is at the core of Data Warehousing, CRM solutions, ERP solutions and a large number of scalable IT solutions, also powering key cloud offerings. Basing his analysis on use cases, Kaj presents how smart migration projects, avoidance of vendor lock in, and identifying the right open solution has resulted in sustainable cost savings for a number of large MySQL users.
Logical and binary backups of thousands of database servers with multiple geographic locations, with complete coverage in 24 hours, requires a massively parallel backup architecture. Decentralized storage, multi-staged repositories, and real-time binary log collection enable rapid disaster recovery, but also provide surprising day-to-day benefits.
Backup is one of the duller administration topics, right? Wrong! Properly configured backups are the key to avoiding data loss, restoring failed databases, and provisioning new servers. In this survey we will cover standard backup/restore techniques such as mysqldump, XtraBackup, file copies,and file system snapshots. Our discussion will cover how each technique works, when it's appropriate to use, and common tricks like combining backups and database replication.
Slave lag is the bane master/slave replication. This talk will explain why slave lag occurs and show you three important ways that Tungsten Replicator can banish it for MySQL slaves. Parallel apply uses multiple threads to execute slave transactions. Prefetch uses parallel threads to read ahead of the slave position and fetch pages that will be needed by the slave. Batching uses CSV files to load row updates in extremely large transactions that bypass SQL completely.
Tired of the intricacies of circular replication? Dreaming of real multiple masters solutions for MySQL replication? Dream no more. Tungsten Replicator, a free and open source replacement for MySQL replication, can build clusters of asynchronous nodes in a matter of minutes.
BigDoor is a gamified loyalty platform that helps websites keep and retain their users. We store each publisher's loyalty economy configuration data in MySQL, plus all of their users' transactional data - points they've received for taking actions that stimulate loyalty, engagement, virality and revenue on their site(s). The transactional data flows into backend analytics systems where it's aggregated for reporting purposes and analyzed to produce optimizations that ultimately improve end-user loyalty.
Growth is good, right? Yes, unless you are the one building and managing a database tier to handle all this growth!
Your company may have built a great new app and has launched it in the cloud. And now you are seeing what many wish for: exponential adoption of your app. But is your database tier really up to the job?
What happens if your database server fails? Can you fail over to a replica quickly? Do you even have a replica to fail over to?
For years memcached has been one of the most widely deployed caching technologies on the planet. It's simple design and easy to use api make it a huge win in most deployments. Over the past several years however another interesting NoSQL project has been picking up steam. Redis promises advanced features and persistent storage that are not available in Memcached. I will compare and contrast these two technologies and give examples of how they work and where they fit.
Joffrey Michaie (SkySQL)
Peter Vandenberghe (JetAir)
Jetair is the Belgian branch of TUI Travel (the largest tourism group in the world) and the market leader in the Belgian tourist industry. Its offer comprises holidays by air, holidays by car and city trips under the brand names Jetair, VIP Selection, Sunjets.be and VTB Reizen.
Seeking better HA mechanisms, JetAir chose MHA to make better use of their existing hardware and more use of their existing server install base.
The common_schema project provides a set of thoroughly documented MySQL views, stored procedures and functions which simplify otherwise complex shell and client scripting tasks. The common_schema is delivered as a self-contained MySQL schema, which is easily installed simply by running a SQL script: there is no need to configure nor to compile; no special plugins are required, and no changes to your configuration. Because common_schema is implemented in SQL, it is independent of any specific operating system, installed packages or dependencies.
With the arrival of a new armada of NoSQL databases chances increase constantly that you will be needing to integrate with one of them. So in this talk I'll be going over concrete examples of crazy MySQL/NoSQL integration:
- Parallel extraction and load of MySQL data into Hadoop
- Real-time update of MySQL tables based on changes in CouchDB
- Extracting JSON information from MongoDB to load it into MySQL
- Populating elasticsearch results with product information stored in MySQL
At Clustrix, we're frequently asked by our customers to help them optimize their query workload for our database. In order to quickly become experts on our customer's databases access patters, we've built a collection of tools to help us profile current database traffic live, as well as track how the workloads change historically.
The breakout session will cover an in depth look at our profile and optimization tools and how we use them. You will get a look at how we go from limited understanding of the application workload to suggesting key improvements to critical queries.
Replication is one of MySQL's most widely-used features, and despite significant improvements over the years, it can still fail. When this happens, it can be due to any number of factors, either internal or external to your MySQL database. For those who do not have a thorough understanding of the MySQL binary log format or the slave's two-phase replication architecture, safely restoring replication while maintaining data integrity can be a daunting task.
Do you occasionally see a problem in your MySQL database, or that you suspect is caused by your MySQL database, but you can't diagnose it because you aren't looking when it happens? This is a very common reason for problems to continue happening for a long time before they are solved. If it hasn't happened to you yet, it probably will someday.
Determining the Query Execution Plan (QEP) of an SQL statement is the primary analysis tool for DBAs. Understanding how to interpret the information from the EXPLAIN command and what additional commands and tools exist to add supplementary information are essential skills that will be used daily in production operations.
The MySQL EXPLAIN QEP is significantly different from an Oracle QEP and Oracle DBAs need to understand and learn the most appropriate way to understand and navigate this information to effective performance tune a running MySQL environment.
Everyone knows that Xtrabackup is a great product and provides point-in-time backups for MySQL. Most companies have some sort of report, whether it be an email or another mechanism, to confirm that backups ran as they should on their system and Ning.com is no different. That said, more was needed out of point-in-time backups so I have created a point-in-time backup system that contains multiple improvements for tracking, transparency and monitoring. During this talk I will present the moving parts of the Ning.com backup system, where we are today and where we would like to take it.