Skip to main content
main-content

Über dieses Buch

Mitigate the risks involved in migrating away from a proprietary database platform toward MariaDB’s open source database engine. This book will help you assess the risks and the work involved, and ensure a successful migration.
Migrating to MariaDB describes the process and lessons learned during a migration from a proprietary database management engine to the MariaDB open source solution. The book discusses the drivers for making the decision and change, walking you through all aspects of the process from evaluating the licensing, navigating the pitfalls and hurdles of a migration, through to final implementation on the new platform. The book highlights the cost-effectiveness of MariaDB and how the licensing worries are simplified in comparison to running on a proprietary platform.
You’ll learn to do your own risk assessment, to identify database and application code that may need to be modified or re-implemented, and to identify MariaDB features to provide the security and failover protection needed by corporate customers. Let the author’s experience in migrating a financial firm to MariaDB inform your own efforts, helping you to develop a road map for both technical and political success within your own organization as you migrate away from proprietary lock-in toward MariaDB’s open source solution.


What You'll LearnEvaluate and compare licensing costs between proprietary databases and MariaDB
Perform a proper risk assessment to inform your planning and execution of the migration
Build a migration road map from the book’s example that is specific to your situation
Make needed application changes and migrate data to the MariaDB open source database engine
Who This Book Is For

Technical professionals (including database administrators, programmers, and technical management) who are interested in migrating away from a proprietary database platform toward MariaDB’s open source database engine and need to assess the risks and the work involved

Inhaltsverzeichnis

Frontmatter

Chapter 1. Drivers for Change

There are many drivers for change in the world of technology and business. We are going to look at a couple of those in the following chapters from the viewpoint of a fictional company that has come out with a new product while at the same time going through a licensing audit. These two catalysts caused the company, Financial Widgets Plus (FWP), to evaluate their current database solution and possible alternative solutions because the cost, along with the overhead of use, of the proprietary solution could no longer be supported or fiscally responsible. They needed a replacement that would propel their new platform into the forefront while allowing them to generate more revenue to drive and support growth.
William Wood

Chapter 2. Requirements and Risk Assessment

The primary catalysts for Financial Widgets Plus (FWP) to make such a monumental change were identified—the primary problem being centered on the ongoing and escalating costs over time of doing business with their current vendor. The benefits of their current DBMS being rock solid, dependable, and having served their needs effectively for many years, were revenue drivers going to be worth the risk to the company would be the next set of questions that would have to be answered.
William Wood

Chapter 3. Database and Application Code

With no showstoppers found with MariaDB, the next phase of validating the solution entailed taking a look at moving on to the implementation phase by evaluating both database and application code for migration to arrive at a feasible plan. Once the work was completed in the previous phase they were pretty optimistic and excited about the MariaDB solution; however, they wanted to analyze the process of not only adding new customers but migrating existing customers on the Oracle DBMS to MariaDB. The LOE was also a concern from the applications side as well as mapping data types, database code changes, and rewrites for PL SQL, and of course sequences.
William Wood

Chapter 4. Making the Decision

This chapter will take us through a summary of the Financial Widgets Plus (FWP) team’s work and culminate with a sample project definition with an executive summary for the team’s presentation in regard to choosing MariaDB as the new DBMS over their existing solution. Even though the raw presentation of the work completed so far speaks for itself, one may find that bringing this all together in a professionally formatted presentation should be the primary goal for any project, much less one with the far-reaching scope of migrating to a completely new database backend for a company’s premier product. As with any good analysis it isn’t just about presenting the benefits, but also identifying risks and mitigations in order to minimize those risks, along with an overall Cost Benefit Analysis (CBA), and that was Vernon’s approach.
William Wood

Chapter 5. MariaDB Solution

As discussed in Chapter 4 in regard to the initial deployment of their MariaDB solution at Financial Widgets Plus (FWP) and keeping with the KISS principle, the team chose to stand up a stand-alone environment with replication. Using this as the basis for their proof of concept work turned out to enable them to get an active MariaDB environment deployed quickly and easily in order to validate what they had already perceived as a viable solution to their database solution alternative. Once the proof of concept was complete, the team then went on to deploy a much more robust high availability solution. Here we will get into detail on the setup and deployments as completed by Vernon’s team, to get them familiar with the database solution by enabling them to rapidly deploy and then extend their MariaDB footprint.
William Wood

Chapter 6. Change as a Catalyst

When Vernon was first presented with the mandate to start researching alternative database solutions for Financial Widgets Plus (FWP) he saw a much larger opportunity at hand. Coming in to a new company that had a database department that consisted entirely of a group of what he termed as Reactive Database Administrators that had created and deployed an amalgamation of one off solutions and had never explored the concept of standardization, he realized that this was the best thing that could happen to not only Financial Widgets Plus, but also to the department that he was now heading up. Where others saw the migration to a new database solution as an opportunity to lower costs significantly and be done with what they perceived as a predatory vendor, Vernon saw this is an opportunity to fix many headaches and problems that had been plaguing the organization for quite some time.
William Wood

Chapter 7. Defining a Roadmap for Success

Taking on such a monumental technology task as migrating to a different DBMS solution involves equally monumental risks, and the only way to mitigate those risks is through proper analysis, planning, testing, and implementation. Not to minimize other areas of technology, but migrating database solutions carries an extraordinary risk in comparison.
William Wood

Chapter 8. Making the Data Move

The next phase in migrating to MariaDB (from Oracle in particular) is making the data move from one DBMS to another successfully, and this was the part of the migration that was very important for Financial Widgets Plus (FWP) to get right for the existing customers and their corresponding production data. All new customers coming into the program would go straight to the new database solution; however, they needed to get an existing customer out there and running as a proof of concept.
William Wood

Backmatter

Weitere Informationen

Premium Partner

BranchenIndex Online

Die B2B-Firmensuche für Industrie und Wirtschaft: Kostenfrei in Firmenprofilen nach Lieferanten, Herstellern, Dienstleistern und Händlern recherchieren.

Whitepaper

- ANZEIGE -

Best Practices für die Mitarbeiter-Partizipation in der Produktentwicklung

Unternehmen haben das Innovationspotenzial der eigenen Mitarbeiter auch außerhalb der F&E-Abteilung erkannt. Viele Initiativen zur Partizipation scheitern in der Praxis jedoch häufig. Lesen Sie hier  - basierend auf einer qualitativ-explorativen Expertenstudie - mehr über die wesentlichen Problemfelder der mitarbeiterzentrierten Produktentwicklung und profitieren Sie von konkreten Handlungsempfehlungen aus der Praxis.
Jetzt gratis downloaden!

Bildnachweise