What's your #cloud #migration #strategy?

What's your #cloud #migration #strategy?

What's your #cloud #migration #strategy?

When you move your IT infrastructure to the cloud - sometimes as a precursor for ML work - you need to do so with a plan. In this video I discuss some of the considerations and how to think about a strategy.

Also is a link to the RPA video mentioned:    • When to use #RPA  

------------------
I provide perspectives in AI and architecture - touching upon different topics.

At times, I also help companies clarify their message in these domains.

If you’d like to work with me, please send me a note (through my website www.drrajramesh.com)

Thanks for watching my videos and for subscribing.

www.drrajramesh.com
www.linkedin.com/in/rajramesh


Content

6.049 -> How to think about your Cloud migration strategy?
8.51 -> Let’s say, you’ve made the decision to move your IT infrastructure and applications
13.719 -> to the cloud as part of your overall AI transformation.
18.3 -> What is your strategy?
20.539 -> First let's clarify what a strategy is.
23.15 -> I’ll use a simple example.
26.18 -> Every strategy has at least one goal.
29.029 -> A young person’s goal might be to be rich.
32.59 -> There are many choices to achieve that goal.
36.05 -> One may be to marry someone with money, another to get a good education and a job, another
43.699 -> to start businesses, another to rob a bank, and so on.
49.73 -> Some may not align with the person’s values.
52.98 -> So he may chose to get rich through business because he has a knack for it.
59.51 -> The choices the person makes towards achieving the goal is your strategy.
65.24 -> That’s it!
66.85 -> If you are not making choices, there is no strategy.
69.76 -> I’ve come across too many attractively formatted “strategy” documents that are not strategy!
78.15 -> Say you are a retailer.
80.29 -> Your web traffic goes up during holiday seasons and you want to be able to meet the demand.
86.44 -> If you have your own IT, then you have to invest in enough IT to take you through the
92.68 -> holiday season, but that same IT will be much underused for 95% of the year.
101.15 -> If you don’t invest up front, then you will lose sales during the holidays.
106.46 -> So, you basically want to reduce your cost and yet ensure scalability.
114.25 -> How will you achieve these goals?
116.03 -> You have two options: (1) outsource your IT to some services company, or, (2) move your
124.25 -> technology to the cloud.
127.21 -> If your software applications were just a commodity then you could go with option one
133.5 -> because it's not a differentiator.
136.22 -> In the early 2000s, AMEX outsourced their IT to IBM at a deal worth about $4 billion
144.89 -> at the time.
145.89 -> On the other hand, if you have applications that differentiates you from others and you
152.451 -> want to maintain control over it then you would choose option two – which is essentially
159.03 -> you are renting out computing resources rather than buying it outright.
164.91 -> Netflix uses Amazon’s AWS cloud.
166.78 -> Say you’ve done some research and decided to move to the cloud to reduce your cost and
176.06 -> ensure scalability.
178.46 -> Right there, you’ve made your first choice: migrate your IT to the cloud.
184.709 -> That thoughtful choice becomes part of your strategy.
189.74 -> The next goal is to actually put your IT on the cloud.
195.43 -> You have multiple options.
198.38 -> One is called “lift and shift.”
200.58 -> In this case you're not making any changes to the software but simply leaving the hardware
205.37 -> behind and moving your software to hardware that's on the cloud maintained by the cloud
212.45 -> providers.
214.37 -> This option should directly reduce your cost and allow you to scale.
217.97 -> So go for it.
219.36 -> Ah, you are not happy with this choice.
223.15 -> Why not?
224.45 -> Oh your software is built in such a way that it still requires a lot of maintenance for
229.81 -> new business requirements and you feel you're not agile enough.
237.09 -> OK, what you're really saying is that the software has to be refactored so that it can
243.93 -> deal elegantly with new business requirements and changes.
248.47 -> So the option of lifting shift is not going to work.
252.569 -> Rather you have to refactor the code.
255.45 -> How and when can you do that?
259.009 -> One option is simply move everything over to the cloud as is, and do a second phase
265.37 -> where you refactor the code.
267.509 -> The problem is that you may not ever go to the second phase and your code will be as
273.461 -> bad as it was.
275.689 -> Another option is to refactor the code as you move to the cloud.
280.57 -> This option has more risk.
284.259 -> As a company you decide that you can come together and reduce the risk.
288.61 -> So you’ve made your next choice.
292.789 -> Great!
294.36 -> Software applications comes in many sizes and forms.
298.61 -> Let's just focus on a web based shopping cart application that your customers used to buy
304.02 -> your products.
305.31 -> Here’s the architecture of this application.
308.639 -> On the backend you have a database – specifically a relational database.
313.8 -> The middle application layer contains the business logic of reading, manipulating, and
318.229 -> writing data back.
320.03 -> Finally, the user interface layer is the front-end screen through which the customer interacts
325.129 -> with the software application.
327.87 -> This is called the 3-tier application.
330.419 -> Overall, this application drives many business process steps or entire business processes.
337.419 -> The customer shops on your website and drops a product in the shopping cart.
342.8 -> Once the customer purchases the product through a checkout process, it triggers a business
347.539 -> process that checks inventory, accepts the payment, and sends a notification to the shipping
354.229 -> department to ship the product to the customer’s address.
358.27 -> The shipping department might have its own three tier software application, to manage
363.12 -> the products that have to be and have been shipped.
366.71 -> Their database may be completely separate because that application was developed for
371.68 -> their need, at a different point in time, with a different set of technologies.
378.599 -> Other business areas might have the same – essentially holding duplicate information across their
383.999 -> databases with different business logic for the same problem.
389.159 -> Having understood this architecture, it looks like we’ll have to make a few more choices.
394.389 -> Let’s focus on integration of systems.
398.659 -> There are many options to integrate such systems to make the end-to-end customer experience
404.669 -> seamless.
406.65 -> Specifically we’ll talk about integrating the shopping and shipping systems
412.129 -> The simplest option is to use a human to read information from one system, and manually
417.279 -> type it into the other.
420.099 -> In the customer shopping example above, when a notification arrives in the form of say
425.41 -> an email to an agent, she reads the content of the email to update the shipping system.
431.68 -> As you can tell, this way of doing things is error prone and inefficient.
439.199 -> A better option is to use RPA or robotic process automation which I describe in more detail
445.949 -> in another video whose link I share in the description below.
451.849 -> Another is to wrap the functionality of applications in APIs or application programing interfaces,
458.339 -> where one application calls another to update it.
462.719 -> However, this causes a many one-to-one integrations to happen, and the complexity increases exponentially.
470.839 -> Yet another option is to use an eventing architecture where system events are dropped in a location
477.509 -> and other systems can pick up and use those of interest.
482.96 -> For example, a checkout event may be dropped in, which could be picked up by the shipping
487.679 -> system.
488.839 -> So you have some architectural choices to make.
493.719 -> Maybe you picked the eventing architecture.
498.36 -> All these choices we made so far – choose the cloud, move and refactor in one shot,
504.689 -> and use the eventing architecture - together make up your cloud migration strategy.
512.93 -> I did not cover the exhaustive list of goals or choices you have to make, but wanted to
519.149 -> give you a way to think about it.
522.56 -> If you are creating a cloud migration strategy, make sure you understand the goals, and the
528.149 -> choices you make to achieve each goal.
532.42 -> If not, you are just getting a fluffy document that’ll go on the shelf!
540.399 -> If you enjoyed this video, please consider subscribing.
544.41 -> For a 1-page visual summary of this video, sign up on my website.
548.5 -> Thank you deeply for giving me the motivation to do what I do.

Source: https://www.youtube.com/watch?v=u_lJ9dKu5Y0