How did you make your transition to the cloud? What worked and what didn't work? - Pulse Q&A

How did you make your transition to the cloud? What worked and what didn't work?

#cloud,#enterprise products @IT Number of answers: 1

Arvind KC, CIO at Palantir Technologies

, answered on 2018-01-26T01:05:24.087Z, 7 months ago

At Palantir, we moved all on prem servers to the cloud (AWS) but did it all as code (as opposed to configuration). There are several reasons for doing it this way and this approach while not new is recently gaining more traction. The idea here is don’t configure anything in your infra, instead describe the end state you want using a declarative language like terraform and then let the tools build the infrastructure for you. This is contrary to the classical approach where it is a combination of code, interspersed with manual config, resulting in fragile infrastructure.
By using this approach, we:
  1. are somewhat cloud agnostic (as to the infra is described in a language that works with all major cloud providers)
  2. don’t have any administrator as a single point of failure
  3. have infra that is repeatable and consistent across environments
  4. have a process that is fully integrated it with VCS, CI/CD so there is continuous deployment and automatic tracking of all changes

upvotes: 7

Comments:

Pulse Q&A

Follow Us

GET THE MOST OUT OF PULSE

At Palantir, we moved all on prem servers to the cloud (AWS) but did it all as code (as opposed to configuration). There are several reasons for doing it this way and this approach while not new is recently gaining more traction. The idea here is don’t configure anything in your infra, instead describe the end state you want using a declarative language like terraform and then let the tools build the infrastructure for you. This is contrary to the classical approach where it is a combination of code, interspersed with manual config, resulting in fragile infrastructure.
By using this approach, we:

  1. are somewhat cloud agnostic (as to the infra is described in a language that works with all major cloud providers)
  2. don’t have any administrator as a single point of failure
  3. have infra that is repeatable and consistent across environments
  4. have a process that is fully integrated it with VCS, CI/CD so there is continuous deployment and automatic tracking of all changes

logo