29 lines
15 KiB
Markdown
29 lines
15 KiB
Markdown
|
---
|
||
|
|
preview_image:
|
||
|
|
hero:
|
||
|
|
image: /icons/containers.svg
|
||
|
|
title: "Best Practices for Infrastructure as Code"
|
||
|
|
title: "Best Practices for Infrastructure as Code"
|
||
|
|
meta_desc: |
|
||
|
|
A talk from the Pulumi 1.0 launch event, presented by Christian Theilemann, Senior Software Engineer at Solvvy.
|
||
|
|
url_slug: best-practices-infrastructure-as-code
|
||
|
|
featured: false
|
||
|
|
pre_recorded: true
|
||
|
|
pulumi_tv: false
|
||
|
|
unlisted: false
|
||
|
|
gated: false
|
||
|
|
type: webinars
|
||
|
|
external: false
|
||
|
|
no_getting_started: true
|
||
|
|
block_external_search_index: false
|
||
|
|
main:
|
||
|
|
title: "Best Practices for Infrastructure as Code"
|
||
|
|
description: |
|
||
|
|
A talk from the Pulumi 1.0 launch event, presented by Christian Theilemann, Senior Software Engineer at Solvvy.
|
||
|
|
sortable_date: 2019-09-30T20:10:38Z
|
||
|
|
youtube_url: https://www.youtube.com/embed/U14WtAaag7g
|
||
|
|
transcript: |
|
||
|
|
All right, everybody. So thank you. Um So I'm actually my name is Christian Timan. I'm a senior software engineer at so, and uh it was just like a big person startup. And as Eric was already saying, we are one of the relatively early customers of uh we started using it in August last year and we use it for almost everything on our infrastructure in the production since about January. And I just want to talk a little bit how we use it, why we use it and what are some of the best practices we had at the time? So about me, yeah, super soft engineer. I focus mostly on infrastructure platform. I make most of our tool decisions, uh provisional infrastructure and make the rest of our engineers a bit more efficient. But by background, I'm actually like a full engineer. I work a lot on web apps and stuff like that and I just happened to work a lot in the infrastructure last year. So um yeah, quickly about so obviously, so we have 50 groups to start up. We do a bunch of fish, our customer service, uh Some of our customers are picked up a link. Uh So when you got a website link and you ask a question here, uh it's actually going to U I and our back end which is a bunch of personality and a bunch of websites to be, to know what his mother was for me. I mean, not answering some of these questions, our stack is primarily on GCP. Um And then the back end we use for the most part P and um and not for the infrastructure but also the application. So that's, it's kind of important we don't like just um but we also deploy into a foster. You're interesting about our stack in detail. You can actually um how do we, how and why do we use our money uh over anything else? Uh So in 2018, we started project to modernize our infrastructure because we had a lot of cost stability and velocity of deployment. And this was not just because we were, there was a lot of things wrong and we fought as right as two, which uh for the most part managed to be hands full and lots of custom bash, a bit of Jenkins and some steps which were documented or not in some way is great. Um A key decision at that time was it was beginning in 2008, so was fairly popular at the time. Uh So we wanted to do something which look very promising and that was, and to run. Uh We decided to use G PE on GCP because it's, it takes away a lot of the man and the itself. Um And we started um yeah, setting up a bunch of GCP projects classes just using terraform and it looks kind of working fine for the basic things. However, where the things were a little bit more ambiguous applications into your classroom and we started using or using, we looked at when the audience actually has this out before and who of you actually likes it. So that's kind of the feeling we have introduced a lot more complexity than problems it solves. In my opinion, we looked at which is conceptually great, but it is kind of awkward language. We would obviously Reflux even tried a terra and they, I think it's not that great minutes and that we used to actually put one for which is like similar to scaffold containers, a bunch of and the poison, but it's super opinionated and it can be really extended for more use cases. So in August, I found the little me, I tried it out and I was from the get go be impressed waiting on how good it was worth for a product. It literally just came out of private i two months ago. And it was honestly at that time, already looking better than a lot of the tools which she had been out there for 45 years and gave a lot of confidence in the company that this is like a good platform and completely, I think some of the, the the two key advantages that I personally seen for me is over what these tools is that it has removed the massive class from point. And one reason for that is like you look at the team, they have a bunch of folks which have been working for, for a couple of years, they have a lot worked a lot in language technology. And what they do is actually they auto generate a large part of the SDK uh by introspecting the open API spec from the and that's when 1.60 comes out inducing
|
||
|
|
|
||
|
|
---
|