Database migrations from closed source to open source have become a particularly hot topic recently as I have been asked by customers, analysts, investors (and a few competitors!) what’s driving the accelerated changes in enterprise and government IT departments.
私たちは、このPostgresへの変更を10年以上追求、推進してきました。 なので、移行は私たちEDBにとって新しいものではありません（私たちとお客様は、Oracleや大規模なDBプレーヤーをオープンソースに置き換えることが「ホットである」と長い間考えてきたからです）。ただし、この質問の本質で私を襲ったのは、データベース移行の市場がいかに誤解されているかということです。 そして、はい、それはが市場の現実なのです。 では、なぜこの市場が誤解されているのでしょう？
新しいアプリ – そこが蜂蜜があるところ
Let’s face it, we are all juiced by creating something new. That’s as true in IT today as anywhere and for good reason. Business and corresponding IT development models continue to go through a big transformation and the high demands for revenue growth demand equally high growth in the IT support they get. Gartner talks about the New Digital Business Model. In Digital Business Key Initiative Overview by Jorge Lopez published 21 July 2015, Gartner states, “Digital business is the creation of new business designs by blurring the digital and physical worlds. An unprecedented convergence of people, business and things will disrupt existing business models. Businesses will introduce new products and services, even new business models, which connect people, business and things (physical objects that are active players and contribute to business value). This will drive revenue and efficiency that will ensure businesses' ability to compete for years into the future.”
A focus on new, incremental opportunities driven by technology understandably draws the significant market attention away from the topic of migration. That’s acutely true in data management these days. By my count there are at least 4 upstart software company “unicorns” (> $1B valuation) that are database players: Cloudera, Hortonworks, MapR (all three Hadoop plays) and MongoDB (document database). Between them they have garnered more than $1B in investment capital. All are chasing new workloads and add a new growth node to the $36B database market. How big that growth node will be is still a massive open question (all together this group’s revenues are still well below $1B or <3% of the market).
I get it. I like this market too. A lot. Look below those unicorns and you see others including my company, EDB with Postgres, and then there’s DataStax with Cassandra and MariaDB with MySQL also getting bites at the new workloads. At EDB, I estimate that roughly 30-40% of all our business today comes from customers who are writing new apps and have strategically selected Postgres as the new go-to open source database. EDB customers developing new applications of engagement include: Clear Capital, WholeWorldBand, KT, Coresystems, and InMobi.
But what about the other 60-70%? For EDB, that’s the other end of transformation and change. And that’s where the migration happens.
Database Migration – That’s Where the Money Is
これはかなりシンプルです。 大きな「絵」を見てみましょう。 データベース市場は、2015年に約36億ドルです。 Gartnerらは、年間約8％の成長率を見込んでいます。nbspこれは、市場が年間約30億ドルを追加することを意味します。nbsp議論のため、30億ドルをすべて上で議論した「新」と呼んでください。 それは非常に大きな"マイグレーション"市場 - 300億ドルを残します。 それはまた、企業内での節約の機会の大きさを指しています。
The transformation that is the “migration market” is happening fast and at a large scale. We see it happening predominantly on premises where the majority of enterprise applications run. Our biggest customers stack up something like this:
- G1000 Telco – EDB Postgresを新しい標準DBMS（オープンソースDBMSだけでなく）として使用することで、数百のアプリケーションでOracleを体系的に置き換え、年に8桁の数字を節約しています。
- EDB Postgres Plusで何百万人もの顧客にサービスを提供する米国の大手保険会社
- Leading global financial institution is aggressively migrating applications from Oracle to EDB Postgres across its organization
- One of the world’s largest stock exchanges by market capitalization has standardized on EDB Postgres for all new applications
For these companies, the common threads in their migration journey are:
- C-level drive to change the economics of IT and use money overspent in DBMS to fund other strategic business and growth initiatives
- Recognition of the massive overspending on their proprietary database vendors (mostly Oracle) and an impetus to change it (pricing and contract pain with Oracle is the single most common catalyst)
- Early POC and proof that open source alternative like EDB Postgres meet the technical and business requirements
One key question I get is, “what about cloud…is that driving the migration market?” Amazon just entered the migration scene with a service to support their public hosted, managed service segment. We have also been serving this segment with AWS since 2012. For large enterprises with complex database environments and database deployment, migration to public cloud has been a secondary or tertiary consideration as our customers recognize it must fit within a much broader set of requirements, planning and initiatives. Our work with Amazon and AWS via our Postgres Plus Cloud Database has shown that cloud migrations are a piece of a total migration strategy (more below).
Migration Strategies & Best Practices
- Build to the big picture
- You will migrate across a spectrum of applications (non-mission critical, mission-critical, home grown, third party COTs) and deployment models (on-premises traditional, on-premises virtualized, private cloud, public/hosted managed service cloud, i.e. AWS)
- 最も成功した顧客は、どのワークロードが移行に最適であるかについての前向きな視点を持っていました。 これにより、成功の可能性を最大限に高めながら、全体的な移行計画を選択して（時には非常に単純に）設計することができました。
- Rewriting applications can crush the ROI. That’s why we developed database compatibility technology. Don’t rewrite and also don't simply use incomplete “translators”. “Migrating” the database schema is a small part of the process. The heavy lifting is getting the app-specific packages, functions, and stored procedures to run without change.
- Rewrites take a long time and open up multiple cans of worms – migrations are much faster.
- Migration is not an “all-or-nothing” endeavor. You have valuable investments in infrastructure, process and staff. All should be leveraged as part of an effective transformation.
- You have spent years capturing the business processes that differentiate your company and deliver the efficiencies that make your business profitable. Don’t throw that away; build on it while deriving savings from a move to open source databases.
- This is the most overlooked part of a systematic approach for database migration. Your proprietary vendors, and in particular Oracle, have engineered their agreements and your contractual relationship with them to maximize your spend and increase the difficulty for you to change.
- Migrating selected sets of workloads to a lower cost alternative such as EDB Postgres, outside of those contracts offers you savings, and leverage in the negotiation for those workloads that demand specific functionality from the proprietary vendors.
- This is not just a technical migration, engage your procurement and financial groups, including the Chief Financial Officer and Chief Procurement Officer and make it part of your company’s overall strategy. This effort will pay off by giving you right sized cost for workloads, but also in gaining you independence and leverage in the management of your other vendor relations.
Take Charge of the Change
The database migration market is now well established and growing quickly. Thousands of our customers have proven that there is an increasingly well-defined model and approach to this change. Lean in and take charge of your database transformation – the returns are well within your control.
Ed Boyajian is CEO of EnterpriseDB.