 I'm sure everyone know this software named MySQL, but this one has kind of a long history now. Original development has started in 1994 and became PowerRank 1995, which means almost 20 years since this project became PowerRank. However, as a really popular open source database in the world, sometimes people who does not know much detail about MySQL, or there are lots of myths, rumors around MySQL. So today I would like to introduce to you US information of MySQL, and we have really interesting future in MySQL development. My name is Yusuke Kajiyama. I'm coming from Oracle Corporation. We have an organization named MySQL Global Business Unit. Actually, I'm part of the original MySQL Arbe, which is a MySQL company, a Swedish company, SmallOne, purchased by Submariner Systems in 2008, and soon after, Big Red Company, Oracle, purchased Submariner Systems. So I've experienced two mergers of small one purchased by Big One, Big One purchased by Big One. That's the history of MySQL, but still MySQL is part of Oracle, and we are an independent organization named MySQL Global Business Unit, which is different from an entire Oracle sales organization. MySQL is under chief corporate architect. Technically, it's a kind of city or type of person, while all entire Oracle database servers coming from south, general middleware, and so on are under business organization. So we are still doing all development and enhancement support services of MySQL by ourselves. The last five years, which means when sub-micro systems became Oracle. Yes, it's already five years ago, some was purchased by Oracle. But Oracle is investing more into MySQL nowadays, double support developers, three-fold, the test engineers, we call QA engineers, and some of them became done. And we do understand that there are lots of rumors around MySQL, and also Colson, Wory, and what kind of FAQ, most frequently asked question, is Oracle kill MySQL? When Oracle kill MySQL, that's another question. But the short answer is no, we're still here, MySQL is still here, and we are accelerating development and prospects. And also, well, first a few years, some became version into Oracle, we have more easy time to contributing into the open source community. But now, we are here, we are part of the open source beds, and we are announcing a lot of interesting innovation today. But what we have done, we have made a lot of MySQL products into the market, GA, general availability, including MySQL summer 5.5 and 5.6, today's MySQL summer major version, as well as MySQL cluster, I'll introduce you later on, a lot of tools arrived. MySQL continue to be the world's most open source database. Yes, Red Bar is a big world database, but MySQL is as a open source database, it's a far more popular database. But where MySQL is popular? Yes, it's a web, web sites, you can name big ones, Facebook, Twitter, these are all kind of famous MySQL users, but they don't bring things. Booking.com is not exception. Booking.com was decided to move out from MySQL, but then came back to MySQL, we see MySQL newest version, MySQL 5.6, which has really excellent features, I'll quickly introduce in later slides. But MySQL's target, or where MySQL is heading to, is web industries, yes, optimize MySQL into web, but this isn't what we have been doing when we were tiny MySQL. As well as embedded views, software, appliances, or network equipment, those components need a database function inside, you can embed MySQL inside, and you don't have to add much main memory or additional storage. This is a part of the big reason Oracle Corporation needed MySQL, because to install Oracle DB, you need a huge amount of main memory. To install your practice software, you cannot ask the customer, hey, please install 2GB of main memory, 2GB of main memory to install our software, because it's using Oracle. But at MySQL, it's easy, no more than hundreds of megabytes of main memory is needed. But a web is another place, MySQL is number one, or the standard of the web industries. So MySQL is improving for this area, as well as cloud computing infrastructure, because we are having a lot of users, both users and paid customers as well, and cloud computing area, starting from Dropbox, or Evernote, I believe many of you are already using part of these ones. And not only software as a service, platform as a service, MySQL is a default or first database as a service of that many platform as a service vendors. Google Cloud Storage, sorry, Google Cloud Platform, they are still having the database as a service, that's MySQL inside. So we are improving our products. First feature I'm introducing is software named MySQL Fabric. This is a framework, it enables high availability, as well as charging cooperation, utilizing MySQL replication. Replication is a feature, which people choose MySQL, that's kind of first reason, one of the reasons, yes it's open source, it has lots of storage engines, it's lightweight, but replication is also a huge reason people choose MySQL. And now this fabric as a framework, enables managing number of MySQL replication configuration, and this group is part of the data, another group of replication is 100 other part of data, the so-called sharing configuration, we can do with this MySQL Fabric. And not only just a replication configuration, utilizing OpenStack, we can authenticate the entire OpenStack-based private server environment, we can tell the application, hey, here's a new MySQL server booted through OpenStack Nova, that's a part of this data management group, and working as a replication master or slave and so on, application do not have to know every single service. All you need is to talk with MySQL Fabric central repository, fetching all the server layouts, and you get an easy access to the entire backend storage MySQL server replication configuration. Let's move on to next. So what we are currently developing is a software named MySQL Server 5.7. This will be the next major version of MySQL Server, which should be able to release by the end of this year. I can tell this to be the by the end of this year, partly because today, sorry, a few days back, this Monday, we announced the MySQL 5.7.6, that will be the final beta version, and in an hour difference module, it's already saying the next version to be the release candidate. So release candidate, there can be a more more release candidate shot, it may come, but it won't take long time to become GA, JR availability of MySQL, which is the production version. With MySQL 5.7, it will be much faster than the previous versions. This is the benchmark of the central benchmark. We actually have an updated benchmark as well, as well as we analyze benchmark results. We are not doing benchmark for marketing. We really hate doing benchmark for marketing. So you can know the reason why it's faster. This is our website, our developers blog, that explains every single details, why it's faster. There are several reasons. We modified a source code, the granularity of new text, making the logs much smaller in the source code level. Optimizer became faster, the data processing algorithm became much more optimized, and so on. But if you are using MySQL server 5.5, with the one-by-one version lower than today's 5.6, you will get instant performance enhancement, just upgrading to the 5.6. And we are almost doubling the performance of the select of the MySQL and MySQL 5.7 still under development. In MySQL 5.6, today's major version, actually, in this version, 5.6 has an interesting feature named NoSQL API. Yes, MySQL server does speak NoSQL API, and which is faster, like for insert operation, data animation operation, NoSQL API for MySQL has 9 times faster than just regular SQL API, but in the next version, it will be much, much faster. Then, if you are an application developer, you need to understand how to improve SQL statements, or if you are a DBA, you need to point out here's the issue in MySQL, sorry, in your SQL statement. MySQL 6 comes with output of the explain, which is optimizer's judgment, how to access it to the data. We can now visualize utilizing MySQL query tool named MySQL Workbench internally, we change the output format of the explain plan, which is how MySQL server judges how to access the data using index, using to the entire table scan, how to join multiple tables. You can see, this single diagram has one big problem in red, which is we are doing a photo scan to a certain table, which slows down all operations. Another problem, we are hearing a lot from the web application or from DBAs, is we found that one SQL statement is causing a huge problem for the entire application of our entire system, which is causing some reason application developers reject it to fix. Or, when we are using a packaged application, not only the proprietary applications, but like almost someone getting into like XAMLIX, we are hearing a lot from the XAMLIX issue. This is some single statement is slow, but no way for us to change that single statement because it's already pre-packaged or using old wrapper, it's not popularization in the so slow SQL statement. We want to change. Yes, now we can do with query like prog, just changing the SQL statement issued by application using this prog, or this keyword was in the SQL statement, just change it in this way and you can fix the issue right away without involving application developers. This is just part of the features we are enhancing in MySQL 5.7, which is the upcoming version. Other than those ones, we are having nice feature named the performance schema. You can lose every single detail of performance of MySQL server. But today I don't have enough time to debate, but I will tomorrow, or maybe day after tomorrow, there is a session of the performance schema. You can know the more details of what performance schema is, what you can get from those ones. Multisource replication, now we can get all the information from multiple MySQL server into my single MySQL and run on the racks. And this multisource replication may be done by other solutions, as I said it's already having this one. But this is a huge problem of multisource replication in general, which is since there are a number of MySQL servers sending SQL statement into one slave server, one database server MySQL as a slave, which will need to be much, no, efficient to executing those SQL statement. But today's MySQL server's implementation or back in MySQL 5.5 or older, or MySQL server folks based on the MySQL 5.5, they never be able to handle properly the multisource operation We introduced kind of baseline in MySQL 5.6 by the 5.7, it will be the five times faster than today's MySQL server for the multisland operation in slave server. Multimaster replication will be part of the MySQL, should be part of MySQL 5.7, again this one over details, you can learn session tomorrow or day after tomorrow. So this is the power of enhanced mental MySQL well made familiar with MySQL server. But let me introduce one more thing, is MySQL cluster. MySQL has two server products, one is MySQL server which is really popular among web application users, but MySQL cluster which is shared nothing, active-active database cluster, which means without having any shared storage, you can create active-active database cluster instantly. So this is the kind of benefits for a lot of small web application to huge scale because it supports scale-out architecture, adding more servers and you can do huge performance. But an active-active database cluster is just one phase of MySQL cluster. MySQL cluster is really unique product. It can be categorized not only out of events, it's not NoSQL. This is true with our new SQL hybrid solution of NoSQL and SQL data. So let me quickly explain who are using MySQL cluster. Originally, MySQL cluster was used a lot in telecommunications industries. Starting from Ericsson, the NOKIA ZMS, or NEC, those manufacturers. They are using sub-sliver database from network equipments. And there is one logo if you are placing a signal pole from your mobile in the middle of the tunnel. And one signal pole, they are also utilizing MySQL cluster for the user management. Then, not only limited to the telecommunications industry, since MySQL cluster does not have any single model of failure, in the middle of the right, there is a US Navy logo. Yes, US Navy aircraft carrier operation management system is run with MySQL cluster. It is pretty much mission critical of the database. And one more thing I can put out on the top, ZINGA, online game, they are using MySQL cluster for the gaming platform. So MySQL cluster is mission critical database as well as perfect database for the social network web systems because on the left-hand side, there is MySQL server. If you use this MySQL statement to MySQL server, they will be duplicated in the data source. At the same time, on the right-hand side, there are lots of NoSQL API coming into one place. If you use the API, MamiCache D API, MySQL cluster suddenly became transactional key value data store. And this transactional key value data store, MySQL cluster, is a big statement. So if you are looking for NoSQL solution, MySQL cluster is a quite a great option and it has a flexibility, speaking both NoSQL KBS API and SQL API. It has a huge high potential as a part of the benchmark for the it's a bit older version of MySQL cluster but with 30 servers, it reaches almost 20 million updates per second. It's perfect for the social game news version of MySQL cluster now it reaches 200 million sub-acts per second. It's a huge number, I believe, I hope. Well, we're utilizing 30 servers but it's not no special service it's regular x86. So this is a potential performance of MySQL cluster but this one is a performance as a NoSQL storage. Using NoSQL API, we have C++ API, this benchmark is using C++ we also have Java API then we can see as an API Node.js API as well. If you're using a SQL statement I may disappoint you because NoSQL API performance is too high it only reaches 2.5 million sub-acts per second. Well, it's quite a huge number as a SQL basis I believe it makes. But again, please remember MySQL cluster is a hybrid database solution for active database cluster as well as transactional key value data store. It's also common in the market to see as of today. So I explain quite a lot of things regarding MySQL or starting with MySQL server 5.7 as well as MySQL cluster. So if you're interested, we have a booth outside of this room as well. I believe tomorrow we have three sessions. MySQL over-education MySQL performance schema and one more session I forgot. It can be the master product. There's several sessions we're going on in the next two days and again if you have any questions I won't put you to answer questions right now or please visit our booth outside. Okay, that's pretty much my session for now I don't see any next speakers. Yes. The next speaker is here. And that was a quick question. So last time I'm aware that MySQL cluster has the size limit for the relational database so it was there and now it was the size. So the MySQL doesn't have any limitation in MySQL cluster. But in the production use it's depending on how much label you can afford. So practical usage of MySQL cluster is two terabytes, three terabytes, is kind of ideal or no, large usage. But it never be that hard to limit. So depending on the configuration we can go over way bigger size. Here this size by spec is like 600x or something. So this is pretty much technical. But practical usage is that's all that matters. So this, again, just go hard a little bit. Thank you very much. If there's no other questions let's give Bruce Gay Bruce Gay a round of applause.