MariaDB SkySQL managed cloud goes live on Google Cloud


cloud.jpg

Builds on cloud-native storage support from its X4 Enterprise platform. MariaDB live now with SkySQL, is the managed cloud database-as-a-Service (DBaaS). Coming to market several years after AWS and Azure introduced their own MariaDB cloud services, the company differentiates SkySQL as a combined transaction and analytics platform.

And MariaDB is charting another path to the market with SkySQL; while ultimately planning to run on all three major public clouds, it debuted with Google Cloud Platform (GCP). It is a reflection of GCPs open source data platform partnership program, which MariaDB joins. This was one of the announcements originally scheduled for Google Cloud NEXT, which is due to run next week, but has been postponed indefinitely due to coronavirus. But MariaDB continues to make full use of the new service.

As an open source database, MariaDB faces well-known challenges in differentiating with large cloud providers that already have well-established competing services of the same platform – in this case Amazon RDS for MariaDB and Azure database for MariaDB. And the strategy repeats the strategy of players like MongoDB, Redis and Elasticsearch: offering more up-to-date versions and more deluxe (or different) features.

So it starts with platform version: out of the gate, SkySQL will be a single dot release (10.4 vs 10.3 for AWS and Azure) ahead, promising to get to the next 10.5 release as soon as the open source project community declares it production-stable . Obviously, feature differences that relate to release version will be constantly moving targets; For example, this means that, for example, the addition of 10.4 application periods in 10.4 complements the time tables introduced in 10.3.

There are other more basic differences to suit the deluxe theme. As mentioned above, there is the paired analytics and transaction support, courtesy of the column store that only comes with MariaDB Enterprise, and the plug-in architecture that makes it more of a real-time component that came with the X4 version back in January. It includes the smart transactions feature that selectively routes queries to row or column stores based on heuristics. There is MaxScale, a proxy that abstracts high availability, scalability and security from the underlying database, enabling more operational simplicity. The enterprise version also allows multiple indexes, up to 128 per. Table. And while there isn’t a differential yet, MariaDB promises that SkySQL will support multi-master distributed transaction processing “soon.”

There are a few key elements to the SkySQL: X4 platform and the cloud-native, Kubernetes-based architecture. Big on Data bro Andrew Brust provided lowdown on the X4 back in January. X4 marked the culmination of a year-long journey that MariaDB went through to unify its platform, as we outlined almost exactly a year ago. The finished product converged transactions and analytics, so instead of relying on data capture change to feed the analytics engine, the storage engines are now plugins for a common platform where captured data is persisted simultaneously in the row and column stores.

But another key to SkySQL is the cloud-native architecture, which is based on a full implementation of Kubernetes, which will eventually allow more flexibility to scale up or down. That’s the kind of advantage that late-game DBaaS services can also benefit from starting with more advanced technology bases.

For MariaDB SkySQL, Kubernetes and microservices out of the gate allow you to benefit from building an elastic and more secure control plan without having to invent it, and it can also make the service more extensible for third-party solutions. It can make a difference down the road given the trend of data warehousing services expanding their footprint as one-stop shops for related processes in cleansing, integrating and transforming data and providing self-service analytics. It is here microsoft, Oracle, and SAP sets the tone. This would provide a golden opportunity for MariaDB to expand its partnership with Google Cloud, bundle Kubernetes, Cloud features, or the portfolio of analytics and AI services.

At the infrastructure level, cloud-native also means SkySQL embraces computer separation from storage, with row-based transaction row tables on block storage, while the column store sits on S3-compliant cloud object storage. For now, SkySQL will require at least one active engine, but in the future it will be fully resilient, meaning the computer could be turned off.

If follows a modular architecture that utilizes ServiceNow to configure and manage workflows, a separate open source server Grafana dashboards and Prometheus log event monitoring as the operational management console and then the database running in a Kubernetes cluster. So, for example, when there is a need to ramp the computer up or down. MaxScale manages the request, which is then executed through an orchestrated workflow in Kubernetes.

For the MariaDB company, this is not the first stack of a cloud service. The original offer, MariaDB Managed Service, was a white glove service similar to traditional hosted services that were not capable of serving a larger customer base. SkySQL is designed more on a self-service model, but is also designed for a larger scale. It supports failover across multiple accessibility zones, self-healing, load balancing for reading and encrypting data on the cord and at rest.

As noted above, SkySQL initially rolls out on Google Cloud with AWS and Azure to arrive later on dates to be specified.



Source link