In order to do this, it helps if you have an application/system where you can separately migrate individual parts or components. It is a step you need to complete, but should not assume that it will confirm that your production service will run.ĭuring the migration we tried, where possible, to accelerate the test migration of production services as soon as we reasonably could. Starting small is a great way to gain familiarity with a new platform and perform basic testing. These often don’t get fixed and can turn around a hurt you when trying to run Production services. Something non-critical (less important) – By definition, this is something that you care about less and therefore are more willing to accept odd issues and failures.They often lull you into a false sense of security. You can always try to benchmark or loadtest but it is usually impossible to recreate the exact conditions you will see in production. Something small – You will never hit any issues/edge cases associated with size or scale.There are some fundamental issues with starting small and outside the critical path:
Our advice is to move through this phase rapidly and consider migrating parts of the environment that matter as this is the only way you can truly shake out all of the issues you will encounter. This is true to an extent, but you have to be careful. Making it real, and as quickly as possibleĬonventional wisdom states that you should start these types of migrations with something small and non-critical because this is where you learn. It was great to see a team of engineers from two separate companies working for a common shared goal.
Every time we found something that could have derailed the plan, the Google team stepped up and delivered. The great thing about working with Google on this was they never shied away from that challenge. In the early days of the project, when we were discussing how quickly could we migrate, we did not want to accept the normal and wanted to set a big, hairy, audacious goal. We found brownbag sessions were the best format for this as they provided a forum for people who wanted to know more and an opportunity for them to ask questions. We had to say ‘no’ to other less important requests coming in from the business and order to do that we needed to ensure the whole company knew why we were doing this. In order to stand any chance of achieving the objective, we needed to minimize distractions as they are always a sink of time and could lead to failure. So how were we able to achieve the migration so quickly? To read this series from the beginning, see Part 1.Īll of the planning and processes explored in parts 1-4 of this series got us ready to build the next generation of Evernote. This is the final post in a 5-part series on Evernote’s transition to Google Cloud Platform (GCP).
0 kommentar(er)
