GitLab Incubation Engineering, 1 Jun 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Incubation Engineering Jamstack -- Update June 1st, 2022

Description

TL;DR: https://gitlab.com/gitlab-org/incubation-engineering/jamstack/meta/-/issues/44

A

Hello, this is the jamstack intubation engineering update, I'm janis. Thank you for tuning in it's been a while, since the last update- and I have a few very interesting things to note one- I have added the developer documentation on the pipeline wizard to the gitlab docs.

A

You can now go to the docs click, gitlab development, ci, cd development and select pipeline wizard to see the full documentation.

A

I hope this gives folks the opportunity to use the pipeline wizard in their tasks and to understand the current capabilities. Please ping me if you feel like there's anything missing from the docs or, if something's not totally clear.

A

Now for the second update, my own use of the wizard in the github page's onboarding process is currently ongoing. I've just been picking up loose ends that I left before going on my co shadow.

A

These are the things I'm working on. This, mr introduces a checklist widget to the wizard and once that's completed, I'm merging this one. This is the mr that uses the wizard itself.

A

So there's another thing that happened in the meantime that I have spent a lot of time. Time investigating cloudfiller announced d1 an sqlite database for the edge, I'm very very excited about that announcement.

A

It allows us to deploy simple databases on the edge as close to the client as you can get. Why is this cool? Most of the recent innovation in the database. Space has been around how to scale huge databases and have them be always consistent, but there's been little new stuff for when you just need a tiny database. But what one that, as performance as possible, I mean you can deploy a small mysql instance somewhere, but depending on where the api sits in relation to that you're. Introducing a latency, db, sharding or replication might resolve that.

A

But that's a ton of work, if you just want to say, store a few comments or don't have a ton of records. So d1 is an amazing solution to that. It's sqlite on an edge worker that basically syncs to object storage.

A

So you have that eventual consistency model where data might not be immediately reflected in other database instances, but what you gain in return is a super lightweight sql database that lives extremely close to the client. It's just perfect for those front end heavy use cases.

A

I think this is a one in a million evolution with a significance similar to remix. Actually, I expect d1 to play extremely well with remix, so I'll now drop everything just to investigate that new feature.

A

Now this was it for this week's update. I hope to see you again next time until then, bye.