Migration on cloud | start picture, skills by pit

Personally experienced two companies from 0 to 1 on the cloud, migration and directly on the cloud, recorded some fun climbing “pit”

Cloud flow + cloud network, application structure

Migration on cloud process + structure diagram

Why the cloud

Of course, each company faces different problems. I can only speak from my own experience of the two companies and some of my own cognition, welcome students to add.

If you’re building your own computer room (IDC won’t talk about this), imagine what your computer room looks like

But it could be this

A little exaggerated, but the actual machine room of their own, who knows

Get into the business

The picture of the machine room is just naughty. In reality, the cloud can be considered no more than several points. Can the cloud solve your key problems?

  • The cost? Will costs come down, and will the cost increases address other pain points? .

  • Security? Can’t find the source of the poisoning? Server security policy? Is there anything you can do about being DDOS? .

  • Operations? Reset skills? Two days before people quit again? Bug fixes are a pain? .

  • Performance? Can’t the machine hold up if the activity prediction and pressure measurement are not in place? Bandwidth full? No ability to scale horizontally or vertically? .

So everyone, what problem do you solve on the cloud? Or just keep up with the trend and be on the cloud from the start?

Why the clouds? What are the “pits” in the clouds? Blog park on the cloud of the road most valuable reference.Memories link

Part from the pit

Start by figuring out your current network structure, which is your network structure in the cloud for your current business scenario. In the cloud everything is a service, there is no hardware. But you still have to have the usual network topology

  • Into: a request to come is how layer upon layer to arrive at your server, encounter failure also want layer upon layer investigation to come over
  • Outgoing: Requests external resources. If you do not need to manage them, simply click on a public networkipAnd then open the

On the cloud to have an estimate of the process, remember to directly buy service resources, here is not our own spent hundreds of dollars to buy 1 core 1G or 3 years of the kind of ha. The specific execution process needs to comb the time cut-off point according to the process. If it is not clear, it is very costly to delay and delay

The pit is so

  • Business manager – cloud docking cloud manufacturers generally have an exclusive business manager, young I thought this must be the cloud official, may actually know where to find the third party. If your consumption ability is very strong, such as more than hundreds of thousands, please directly contact the official, big customer. At this point it may be an official business person who connects with you. How can you expect millions of cloud users? Small customers are outsourced by third parties. If you use “Dina *” to contact your customer service manager. So the difference is. One has official authentication, one does not just hang a title.

  • The repair orderWhen it comes to coordination, you might think the cloud experts are working directly for you. Design Tucson broken, in fact, sometimes work order back and forth a few times, you smell the taste of amateurI’m going to file a complaint against you for offering up your killer. At this point he will transfer you backstage, so you have to wait patiently. This time a different number to solve your problem. Usually he can really solve your problems. Don’t ask, ask is experienced. I had an interview with an operation and maintenance man. He said that what he did was the customer service of cloud manufacturers to solve the problems of customers’ work orders. If it doesn’t, it’s going up. So your first layer of troubleshooting for you is these outsourcing personnel if you are a big customer emergency please timely contact your business manager — (urge) coordination

  • Domain name, record, subject – these are all submitted data types, the rest is, and so on. Among them, one cloud account can only be bound to one subject, which has 8 pits in 10 community feedback.

  • Welcome the students to add, so the original series to be continued…

“Pit” of their own digging their own jump and climb

Of course, some are their own POTS

  • Figure out the units of measurement – Figure out the units of traffic and broadband in your monitoring system. For example, KB/s and Kbps are two very different things. Pressure measurement and monitoring must not be confused, the budget is either low or high, monitoring threshold setting is not reasonable.

  • Product service charge method — make clear, what press time, according to the amount, combination of resource package, can not be counted into the resource package, otherwise you are today to apply for money, tomorrow to apply for money. It’s all small stuff, bigger stuff like when the service stops and the resource is expected to be permanently deleted, there’s no place to cry. Application resources to be recovered, as long as you take up the resources will be charged.

  • Take a good look at the product documentation anyway — you can avoid most problems. Product restrictions? If online products and services are incompatible, avoid in advance to avoid wasting time. Mail port, as well as their own people say a little pit cloud shield ah, their pressure test before the application to add a good white list.