While there are many common characteristics found in
successful migrations, there is no magic solution that will
work for all scenarios. This is a list of considerations
as you plan your Apache Solr migration from on-premise to the
Google Cloud Platform.
Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...
Five Considerations When Migrating Your On-Premise Solr Infrastructure to Google Cloud Platform (GCP)
1. Five Considerations When Migrating Your On-Premise
Solr Infrastructure to Google Cloud Platform (GCP)
+
2. Moving all or a portion of your IT infrastructure to the cloud is a rapidly growing
trend. Moving a meaningful portion, but perhaps not necessarily all of your IT
assets, to the cloud is considered a migration. Migrations may take on many
different forms - from moving a single data center, a group of data centers, or a
set of applications regardless of which data center they may reside. Our focus
will be around migrating your on-premise Apache Solr infrastructure to the
Google Cloud Platform. Whether you’ve completed many migrations or if this is
your first one, migrating your Solr infrastructure does pose some specific issues
that should be carefully thought through.
Introduction
3. 3
The decision to migrate to the cloud can be
driven by a number of factors including:
Cost reduction
Improved Uptime and Disaster Recovery Scenarios
Dynamic Scaling of Search Infrastructure
Increased developer productivity
While there are many common characteristics found in successful
migrations, there is no magic solution that will work for all scenarios.
The following is a list of considerations as you plan your Apache Solr
migration from on-premise to the Google Cloud Platform.
4. 4
1. Where Are You in Your Migration Expertise
and the Criticality of Your Solr Application?
Starting the migration process with less critical and less
complex applications in your portfolio creates a solid learning
opportunity for your team and lowers the overall risk for any
migration. During these initial first “pilot-migrations”, you will:
• Gain confidence in migration while not risking mission critical
applications in the early learning stages
• Execute best practices that can be applied to future iterations
• Identify and fill missing skills and processes and fill them prior
to higher risk migrations
The key is to understand your own level of migration expertise and where your Solr
infrastructure lies from a mission criticality perspective and then planning accordingly.
5. 5
2. You Separate Cloud Infrastructure from
Managed Services and Professional Services?
To better understand your cost components, it’s best to separate
Cloud Infrastructure (Unmanaged Services) from Managed Services
and Professional Services required to perform the migration. There
is a difference between cloud infrastructure (IaaS) and labor to:
migrate the infrastructure to the cloud
manage that infrastructure day-to-day and
underlying Cloud providers infrastructure costs.
Successful cloud migrations separate cloud infrastructure
from “hands-on keyboard” services and labor, or other
managed services purchases.
6. 6
3. Is There an Apache Solr as a Service
Solution on GCP?
Is there a service that can help accomplish your goal?
To make an education decision:
• Start your research with an internet search looking for Solr
Service that is offered on top of Google Cloud Platform
• Review the websites and learn about the different service
providers pros and cons
• Contact the service providers that meet your initial requirements
and then ask these providers the deeper questions related to
your use case
Once this is done you are ready to make critical decisions around
your migration.
7. To download the complete white paper, please visit
www.SearchStaxWhitePaper.com