Datasets:
willtheorangeguy
/
2021-Ship-It-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.8k
[3168.86 --> 3170.00] We back every hour.
[3170.28 --> 3171.42] We do like a full backup.
[3171.72 --> 3171.86] Yeah.
[3171.88 --> 3175.38] And we can restore from backup within two, three minutes.
[3175.84 --> 3182.58] So a blank node can pull the backup down from S3 and boot up in three minutes.
[3182.58 --> 3183.90] We'll have less downtime.
[3184.08 --> 3185.42] And it's a very simple procedure.
[3185.80 --> 3187.24] Now, would I choose a managed?
[3187.32 --> 3187.44] Right.
[3187.48 --> 3191.46] You've got a potential data loss issue of like up to an hour, right?
[3191.54 --> 3194.50] Half an hour median data loss if you lose the PV, right?
[3194.72 --> 3195.06] Exactly.
[3195.14 --> 3195.34] Yes.
[3195.64 --> 3197.34] But that's a trade-off that you're willing to make.
[3197.38 --> 3197.76] That's fine.
[3197.84 --> 3198.46] That works great.
[3198.62 --> 3198.90] Exactly.
[3198.90 --> 3204.66] And if I was to choose any PostgreSQL service, type of service, I would just go for a managed
[3204.66 --> 3207.10] one, like CockroachDB, something like that.
[3207.22 --> 3211.06] I mean, that's what I'm thinking because it's a really hard problem to solve.
[3211.54 --> 3214.30] I've been trying to solve this for like a couple of years.
[3214.58 --> 3218.08] I don't think I have in like a different context because it's really difficult.
[3218.34 --> 3224.52] I got to tell you that I love the solution you just talked about because too many companies,
[3224.72 --> 3228.60] and I've heard other people say this, not like this is some insight that I have, but
[3228.60 --> 3230.24] I agree with it 100%.
[3230.24 --> 3234.50] Too many companies look around and they see all this really interesting and production
[3234.50 --> 3238.18] grade hardened technologies coming out of Google and Facebook and other companies
[3238.18 --> 3238.66] like that.
[3238.66 --> 3241.84] And they think, oh, okay, well, if we're going to play in the cloud, we got to have
[3241.84 --> 3242.62] that, right?
[3242.86 --> 3243.66] You don't.
[3243.96 --> 3250.36] And if you try and build your system to be at that level, it's going to drag you down
[3250.36 --> 3251.56] with the weight of it, right?
[3251.90 --> 3255.88] And you looked at it and you said, yeah, we can, you know, worst case scenario, we lose
[3255.88 --> 3256.24] a PV.
[3256.42 --> 3259.90] We can handle half an hour's worth of data loss, right?
[3260.38 --> 3261.92] It's not that big of a deal.
[3261.92 --> 3267.40] Then you can go with a single instance of Postgres without replication and you are fine and your
[3267.40 --> 3269.06] life is so much better, right?
[3269.20 --> 3274.42] So I love that you had the self-awareness as a, you know, organization to make that choice.
[3274.74 --> 3274.84] Yeah.
[3275.04 --> 3276.18] We don't use PVs.
[3276.34 --> 3277.90] But I don't have time for that story.
[3279.50 --> 3281.86] Do you use the host disk for that or what do you do?
[3282.06 --> 3282.48] Oh, yes.
[3282.70 --> 3284.24] It's like 10 times faster.
[3284.96 --> 3285.18] Yeah.
[3285.48 --> 3286.66] Like we never lose that.
[3286.92 --> 3287.32] You don't care.
[3287.32 --> 3290.82] So it doesn't mean that like when you're rolling hosts under your cluster, you need
[3290.82 --> 3292.16] to probably call downtime, right?
[3292.18 --> 3292.84] You need to stop traffic.
[3292.84 --> 3293.58] We have a single host.
[3297.26 --> 3298.40] It's so good.
[3298.62 --> 3299.46] It never went down.
[3302.96 --> 3304.92] We have a much better integration with the CDN.
[3305.02 --> 3309.42] And what that means is that even when the origin is down, we serve stale content.
[3309.82 --> 3315.58] And unless you do posts or patches or anything like that, gets, it works.
[3315.58 --> 3320.58] And parts of the website may be down for most users, but you get your MP3s.
[3320.88 --> 3321.98] We'll serve that content.
[3322.24 --> 3322.94] We'll get the pages.
[3323.84 --> 3328.60] And basically what you're telling me is, boy, life is easy when you're a read-heavy workload.
[3328.72 --> 3329.26] I'll tell you what.
[3329.82 --> 3331.06] Yeah, it is.
[3331.54 --> 3332.58] It definitely is.
[3332.66 --> 3336.78] And if we were to, for example, if we had to have the database up, I really do think
[3336.78 --> 3341.22] that going to a managed service, regardless who manages it, who manages that, it's a much
[3341.22 --> 3341.98] better proposal.
[3342.24 --> 3342.68] Oh, for sure.
[3342.68 --> 3346.38] All the backups, like all the replication, all that stuff, it's managed.
[3346.66 --> 3347.72] You don't have to do that.
[3347.74 --> 3350.24] And you're just consuming the PostgreSQL interface.
[3350.38 --> 3350.76] That's it.
[3351.10 --> 3353.16] So that sounds like a much better proposal.
[3353.22 --> 3353.80] Like a CDN.
[3353.88 --> 3354.96] Would you run your own CDN?
[3355.14 --> 3355.54] Maybe.
[3356.00 --> 3357.84] I mean, if you're big enough, you'll have to.
[3358.24 --> 3359.62] If you're that scale, sure.
[3359.92 --> 3360.08] Right.
[3360.30 --> 3366.52] And another thing about running databases inside Kubernetes is that you could think of
[3366.52 --> 3367.90] it as almost addicting.
[3367.90 --> 3372.16] Because once you make the decision that, well, we're not going to use an external database
[3372.16 --> 3372.64] provider.
[3372.64 --> 3375.34] Instead, we're going to just run them as stateful sets inside Kubernetes.
[3375.54 --> 3378.22] And we believe in the Zolando operator, for example.
[3378.36 --> 3378.50] Right.
[3378.56 --> 3381.70] Well, you're going to find that your developers are naturally just going to be provisioning
[3381.70 --> 3382.26] databases.
[3382.26 --> 3389.20] And that's going to result in multiple stateful sets, not schemas in a large existing Postgres.
[3389.38 --> 3390.94] It's just naturally going to proliferate.
[3391.60 --> 3396.16] And that's the headache that you're going to feel, is that suddenly we have a client who's
[3396.16 --> 3399.00] got hundreds of Postgres's.
[3399.20 --> 3401.02] And I'm not going to name the client, obviously.
[3401.26 --> 3403.30] But I will say they're running them wrong.
[3403.40 --> 3404.10] And they know it.
[3404.20 --> 3404.52] Right.
[3404.52 --> 3408.42] It's technical debt that we're helping them dig out of.
[3408.58 --> 3413.00] But it's a huge pain, huge cost for them.
[3413.34 --> 3414.62] Once you get to a certain scale, you're right.