 Selamat malam. Semua kalian sudah tau saya sebelumnya. Jadi, kita akan berbicara tentang SKL 8.0 Roadmap. Sebelum itu, saya akan memperkenalkan diri saya. Nama saya Ricky. Saya adalah konsultant sel di SKL di ASEAN. Jadi, seperti yang kalian tahu, pada saat ini, kelebihan saya di SKL 5.7, yang sudah keluar sekitar 1 tahun plus. Jadi, sekarang adalah masa untuk versi baru untuk keluar. Pertama, kalian bisa mengetahui bahwa jumpa di versi dari 5.7 jumpa ke 8.0. Apa yang terjadi? Sekarang, kita memiliki produk yang lain disebut SKL Cluster. Ini adalah versi 7.5. Sebenarnya, kita memiliki 2 versi yang berbeda untuk software yang berbeda dengan banyak orang. Jadi, kita ingin memperkenalkan satu nombor, yang namanya 8.0. Jadi, semua orang akan datang dalam versi yang sama. Di tradisi SKL saya, kita memiliki banyak perubahan. Setiap versi meja-versi. Dan salah satu hal-hal yang penting adalah performa kursus. Nanti, saya akan menunjukkan bahan-bahan dengan prosesor dan segala-galanya. Ini adalah bahan-bahan. Saya akan menjauhkan. Sebenarnya, meja-versi saya di sini, beberapa mereka di sini. Mereka telah berhasil memperkenalkan meja-versi 5.7 untuk mencapai performa yang lebih baik 3 kali. Kita memiliki banyak pengalaman aplikasi. Jason juga kita memperkenalkan sebuah data natif di meja-versi. Kemudian, kita memiliki meja-versi 5.7. Kita memiliki aplikasi group bersama Shell & Router untuk membuat meja-versi 5.7. Dan meja-versi 8.0, kita memiliki perubahan dari terakhir. Kita memiliki banyak hal-hal yang lain. Kita memiliki Jason. Kita memiliki lebih banyak fungsi Jason. Kemudian, banyak hal-hal yang lain, seperti meja-versi data, meja-versi unik, kita tidak memiliki fungsi dan segala-galanya. Jadi, meja-versi 8.0 memperkenalkan meja-versi 4.0. Pertama, memiliki meja-versi mobil. Kemudian, meja-versi developer, meja-versi data dan stabilitas. Sekarang, kita akan memiliki seluruh data-versi yang berbicara tentang meja-versi. Dari 10.00 am-4.00 pm. Berbeda-beda developer akan menjelaskan modul-modul-modul mereka. Di mana mereka menghormati banyak hal-hal meja-versi, banyak perubahan meja-versi 8.0. Dari tempat mereka. Pertama, di meja-versi mobil, kita sebenarnya memiliki meja-versi GIS. Terakhirnya, kita memiliki meja-versi GIS dari 5.7. Sekarang, kita memiliki lebih banyak hal-hal. Seperti mereka, kita memiliki meja-versi 5.7. Jadi, kita memiliki lebih banyak fungsi. Sekarang, kita memiliki meja-versi 8.0. Bagaimana memiliki meja-versi? Semua orang, apabila kita berbicara tentang meja-versi mobil, kita harus berbicara tentang meja-versi. Semua orang, tidak pernah memiliki meja-versi di WhatsApp. Tidak ada orang, kan? WhatsApp, Facebook, Twitter, pasti kita memiliki meja-versi satu sama lain. Sekarang kita memiliki meja-versi, kita memiliki meja-versi jasun dari 5.7. Jadi, kita memiliki lebih banyak fungsi jasun, seperti meja-versi juga. Kemudian, kita memiliki meja-versi XDEV API. Sekarang, dengan semua ini, kita memiliki meja-versi juga. Kita memiliki meja-versi. Jadi, bagaimanapun kita memiliki SQL dan tidak memiliki SQL bersama-sama, kita tidak perlu memiliki SQL untuk meja-versi dan tidak memiliki meja-versi dengan database. Kita memiliki meja-versi bersama-sama, dan kita mendukung mereka. Jadi, sekarang kita memiliki meja-versi database. Yang penting untuk meja-versi dengan ekspresi meja-versi. Kita memiliki meja-versi. Saya tidak memiliki meja-versi dengan terlambat. Karena setiap semua meja-versi akan digunakan dengan lebih detail esok oleh pembangunan kami. Jadi, apa yang saya lakukan sekarang adalah memiliki meja-versi untuk mereka. Mereka adalah meja-versi. Jadi, dengan ekspresi meja-versi dengan meja-versi, dengan meja-versi sebenarnya kita memilih banyak meja-versi, banyak meja-versi untuk membuat meja-versi. Kita memiliki fungsi meja-versi. Kita memiliki fungsi meja-versi dengan banyak meja-versi dalam area analitik. Ini membuatnya lebih mudah untuk memiliki fungsi meja-versi. Mereka memiliki fungsi meja-versi. Jadi, ini adalah untuk membuat hal lebih mudah untuk pembangunan untuk membuat aplikasi meja-versi. Karena skip-lop, no wait, keadaan meja-versi dan keadaan meja-versi kita memiliki lebih banyak keadaan dan meja-versi dalam keadaan meja-versi. Mereka memiliki memiliki lebih banyak meja-versi dan keadaan meja-versi dan keadaan meja-versi tidak pernah menggunakan meja-versi sebelumnya. Semua orang sudah menggunakan meja-versi, kan? Jadi, saya rasa pada saat-saat kamu akan memiliki pada saat itu, baiklah, biar saya memiliki pertanyaan saya. Kamu pernah memiliki memiliki keadaan meja-versi dalam keadaan meja-versi? Sebelumnya, sekarang memiliki keadaan meja-versi. Kemudian, kamu berpikir, oke, apa jika saya memiliki keadaan meja-versi dan saya memiliki keadaan meja-versi atau saya ingin memiliki keadaan meja-versi dan saya ingin melihat bagaimana Beberapa bukuan. Tapi jika Anda menghantar keadaan meja memikiran, ia akan mengatrihkan keadaan saya�an. Chaat mata saya. Kamu tidak Ass guidelines kelihatan bersih dipakai ke tempat anda tapi bahkan kamu ingin bahwa tidak ada angk detik Canál, kamu ingin lihat bagaimana ia berguruh. Sekarang, kamu bisa menggunakan easel minis, So it will just use it, it will just, it will not use the index as simple as that. So at that time if you think oh, now it become a little bit faster because it is using another index somehow, right? So now after that you can simply remove the old index that you make invisible, that's all. Set session variables, descending indexes, okay, descending indexes because we, the current B3 indexes in InnoDB actually is what's made for a scan forward index. It's not made for a backward scan. So now with this is descending index, now we have a ascending index and descending index, both of them are about the same speed. Expansive genes, okay, we put more ability on the inside, right? Histogram, we add more histograms, we add histograms in common schema. Better cost optimization optimizers, we actually improve the optimizers. Tomorrow there is going to be a detailed talk about optimizer. Transession scheduling. Resource group is very interesting. Is that in that now you are able to tie down to make a resource group for different, different purpose. Let's say you have a system consisting of six core, right? You make the resource group, resource group. One first resource group is four is you assign to two core. Second resource group you assign to four core, four core of CPU. So different core. Now let's say you have a SQL that you want to prioritize, like first priority, right? Because you want it to be fast and then finish fast. So you want assign it into resource group that have more cores, let's say. So you can run the query and then follow by the resource, which resource group you want to run it on. So it will run on the, let's say, second resource group, which has four cores. So, and then there is another last priority SQL, you can run it on the first resource group. So now we have this resource management. All right. So to make applications more stable. Now we have, you know, RB clusters. This one is already from the 5.7. 5.7, we have this active, active cluster, which is make with the conflict detection for on a multi primary. So in this sense that all, in the minimum server is three. So all these three can run retry. And within this you will have a conflict resolution algorithm. It means to say that let's say at some point in time, you have a conflicting transaction running on both, on two nodes. And then when they replicate, they found out that, oh, there's conflicting transactions. One of them will be rollback. One will be let to run and apply in order to not to break the replications. And this is already built inside. So data dictionary and security enhancements, like roll dynamic privileges, which is more granular privilege and transparent data encryption. I think there is another slides on that. So SQL roll is basically talk about, now we have a roll. So this roll is basically is something that you can assign to user. It's basically for a better user management. You guys have know that the meaning of roll, right? So basically let's say you create a roll and then you put in all the privileges that necessary for this roll. And then you have a number of user. And then you want this user to have the same privilege. If you don't have this roll, that means you have to assign all the privilege, all the privilege one by one to all these users. But since you have this roll, or that already have this all privileges, you simply grant this roll on the user. So it simplifies the user management very much. Atomic access control as well. I let the tomorrow we have this session, especially for that. Dynamic privileges is more to find a great administrative level. So some privilege that we have at this moment is very much have too much, I would say too much privilege inside one single privilege, like a super privilege. But now we have more choices for this privilege instead of just one single privilege to have too much power. TDE for logs, now we can encrypt the redo, undo, and binary logs. Last time the transparent data encryption only covers the data files. Which means that your binary, the rest of these logs are not encrypted. They are still able to be read. But now it's also encrypted. And also enhance password options, password reuse policy, history, when you need to actually change the password and everything all can be set in the password options. In myScale 80. All right. That's basically the end of my presentation. It's very short. And it's basically to set a stage for tomorrow. It's just a brief of what you have, what you get in MyScale 80. Okay. So any questions or anything that you have in mind at this moment? Concerns, comments, feedback. We will appreciate it. It's already. It's already. Oh, okay. It is targeted to be launched around 2 months from now. May June timeframe. May June timeframe. But the speakers are there in our developing files for releases. Ya, sure. I mean, if you guys want to try it out, you can always download it from MyScale.com. But it is still in release candidate version. Ya. But you can, most of the features already there. I don't really think that we have another significant new features that is going to come out soon when it's launched. What do you think about what you see in the MyScale 80.0? Anything that you think is missing there? Anything that you really want to have? Any features that you really want to have in MyScale 80.0? Partition. Well, MyScale already have a table partitioning. We support range list. Ya, exactly. New features. Any new features? Is that the main point of partitioning? Maybe you would like to know? Anything that you think is missing in partitioning? Ya. Partitioning is now native. Ya, it's native. Which means your storage engine now is to support partitioning natively. Ya. Long back I was using 5.5. Oh, 5.5. Ya, 5.5. Ya. I'm not sure if you can answer this but how do the MySQL and Oracle database use interact? Well, Oracle has a databases superior in its features, but it costs a lot of money so, do those themes work together, or between developing an open source database and All right. I can answer that. So, basically, first of all, our team is, we have our own team. We have our own developer team. Oracle Database developers is never mixed together with the MySQL developers. Basically, with the organization structure, Oracle is sitting together with its own division, like Oracle Database, Middleware, Oracle Applications, and Oracle Systems. They are all in one single big structure, myself. But for us, we are actually on the side. That means we call it global business unit, so we are like subsidiary. And we have our own line of reporting. We are not reporting to the CEO that is in charge of the whole Oracle Database and the whole Oracle product. We are actually reporting to the chief corporate architect, which directly report to the big boss. So, we have our own line of reporting managers, directors, and everything. And we are not mixing together. There is very rarely that we have to work together. Probably one of the rare instances that for the MySQL plugin for Oracle Enterprise Manager, that one is definitely going to work together with our monitoring team. So, apart from that, we have our own developers. They have their own developers. Are you friends or foes with MariaDB or, say, Facebook branch? Do you take pictures? Do you share those? Well, I would say, first of all, with Maria. Maria is used to be very close in terms of code with us, but now it's already diverting, especially starting from 10.2, and now it's 10.4. Call it even now? 10.3. Not yet, just like MySQL. Right. So, we are already diverting. They have their own vision. We have our own vision. So, I have to say that sometimes, I have to say that we definitely overlap with each other. So, you're right. We sort of compete with each other. Yes. And to answer to your questions about MySQL with Facebook version, now, our relationship with Facebook is very interesting in the sense that they are basically, what they do is they take our open source code. They modify it. They put more plugins, features, and everything. And they're all out in their environment. All everything looks good. Then, what they do is they contribute the code to us. We are not used to MySQL. MySQL. To MySQL. That means we have to support them when we put that code in our own code. So, this is like the win-win relationship with Facebook. By the way, if maybe you already know that Facebook developer speed is almost as big as us. So, their skill is on par with us. And they are contributing a lot, of course, towards us. We are one of the main people. They are our very good friends. And they are MySQL for persons specialised for them. It's our friend. Yes. It's definitely our friend. And MySQL as a whole, to each money, to each MySQL, we get feedbacks. We get feedbacks. It's our friend. Yes. The database student of Facebook, Mark Callaghan, is very giving a lot of feedbacks. His blog is full of a lot of technical stuff. That is the things that he thinks about us. It's only he right there. And he thinks that he right this. We always take very seriously. Thank you. Thank you for asking it. I got a Facebook page of Facebook page of Facebook, I just came to consume some Prox TV. There was what? Prox TV. Prox TV? Yes. Facebook is already migrated to 100% to Prox TV. So, I just quoted the engine to not run. Like Perkan already did it. Dan kemarin itu... ...dia sudah di tengah-tengah. Bagus. Pada saat ini, saya tidak mendengar... ...berapa plan untuk pergi begitu. Oke. Tidak. Jadi... ...tapi hal-hal yang mungkin bisa berubah. Saya tidak yakin. Kita lihat. Karena kita adalah teman yang baik dengan mereka. Siapa tahu? Baiklah. Ada lagi pertanyaan atau apa-apa? Oke, kalau... Apa yang kamu pikir dari LSM? Tidak. Mereka baru bertanya tentang TV Rock. Jadi apa yang kamu pikirkan... ...dengan TV Rock Structure? Kamu mungkin ingin meletakkan TV? Tidak. Saya hanya mencabar. Tidak, tidak, tidak. Tidak. Tidak. Kamu bisa mencabar. Kamu bisa mencabar setiap kali. Baiklah. Oke. Jika... Sekarang ini akhirnya. Jadi... ...menurut saya... ...tomonglah ke bilik yang sama. Ini akan mempunyai... ...mempunyai banyak hal yang datang. Kita mempunyai banyak... ...punyai banyak superstars di sini. Performans schema. Optimizer, JSON. Securiti dan... ...EDL, data dictionary dan sebagainya. Ini akan menjadi sebuah belas... ...untuk esok. Jadi... ...menghantar. Oke. Terima kasih banyak, guys. Terima kasih banyak.