WEBVTT

NOTE
This file was generated by Descript 

00:00:00.239 --> 00:00:00.960
Raphaël: Hey friends.

00:00:01.020 --> 00:00:04.260
And welcome back to the
Chewy podcast right now.

00:00:04.770 --> 00:00:08.880
I'm going to sort of revive this thing
and do something very different with it.

00:00:09.330 --> 00:00:13.530
Um, essentially, I'm just going to
give you updates on Chewy and what

00:00:13.530 --> 00:00:18.810
this, uh, well, Chewy the Chewy
Stack and what this thing actually

00:00:18.840 --> 00:00:21.540
sort of is what it's turning into.

00:00:21.959 --> 00:00:24.869
Um, Mainly development updates.

00:00:25.020 --> 00:00:27.479
Uh, how, how we're building it.

00:00:27.570 --> 00:00:30.570
Uh, I guess at the moment,
mostly me building it.

00:00:31.049 --> 00:00:33.900
Um, and what's what's going on there.

00:00:34.680 --> 00:00:39.390
So, yeah, that's what the, uh,
the Chewy, the Chewy podcast,

00:00:39.390 --> 00:00:44.670
or as I'm kind of renaming it
code named Chewy, just because.

00:00:45.269 --> 00:00:47.879
Anyway reasons, uh, podcast.

00:00:48.570 --> 00:00:50.239
Um, So.

00:00:50.739 --> 00:00:53.289
Bit of context.

00:00:54.039 --> 00:01:00.550
Uh, for people who are new to all
of this, which is almost everyone.

00:01:01.060 --> 00:01:04.750
Except maybe like a dozen or more people.

00:01:05.140 --> 00:01:08.340
Um, Basically the Chewy Stack.

00:01:09.090 --> 00:01:11.040
Is our attempt.

00:01:11.460 --> 00:01:20.280
To make it a lot easier to deploy a
complex microservice-based applications.

00:01:21.210 --> 00:01:27.750
Um, by essentially packaging up a
really nice stack that we've used as a.

00:01:28.250 --> 00:01:29.030
More context.

00:01:29.480 --> 00:01:33.410
Uh, the Chewy Stack is being developed
by Éphémère Creative, which is

00:01:33.410 --> 00:01:35.300
a small digital product studio.

00:01:35.900 --> 00:01:36.380
And.

00:01:37.160 --> 00:01:38.300
Back to what I was saying.

00:01:38.720 --> 00:01:44.420
We, if our creative have used this stack
across a lot of projects and we find

00:01:44.420 --> 00:01:48.350
that it's a really good experience,
but it's a lot of work to set up, to

00:01:48.350 --> 00:01:49.970
set up all of these microservices.

00:01:50.450 --> 00:01:56.150
Um, that that make up the system, but
once everything is set up and configured

00:01:56.150 --> 00:02:01.190
for development and you have a nice,
uh, Continuous delivery pipeline.

00:02:01.460 --> 00:02:03.890
It's really fun to build with.

00:02:04.390 --> 00:02:07.330
And so essentially we're
building the Chewy Stack.

00:02:07.659 --> 00:02:11.260
To make it easy to set up
those different components.

00:02:11.860 --> 00:02:12.909
And to deploy them.

00:02:13.839 --> 00:02:15.190
And specifically.

00:02:15.730 --> 00:02:19.600
To run them locally and deploy
them to different environments

00:02:19.600 --> 00:02:21.370
and to manage those environments.

00:02:21.700 --> 00:02:27.100
So the idea is you should be able
to create a Chewy Stack application.

00:02:27.880 --> 00:02:30.880
And you should be able to say,
yep, I want to enable off.

00:02:30.940 --> 00:02:34.719
And I want to enable whatever
different parts of the system.

00:02:35.320 --> 00:02:37.329
Um, And.

00:02:38.140 --> 00:02:42.370
Then you should be able to say, yep,
create a staging environment, uh, make

00:02:42.399 --> 00:02:45.459
it a single, uh, digital ocean droplet.

00:02:46.180 --> 00:02:49.269
Uh, of whatever size and deploy.

00:02:49.690 --> 00:02:55.690
And now I'm going to set up a
production environment and make it a.

00:02:55.839 --> 00:03:02.680
Uh, managed Kubernetes cluster on digital
ocean and deploy, or maybe it's an EKS

00:03:02.680 --> 00:03:10.540
cluster or it's a GKE cluster or a VM,
uh, on, on Google cloud or, or an AC

00:03:10.540 --> 00:03:15.279
two instance like any one of those,
we'll make sure there's deployment

00:03:15.279 --> 00:03:20.740
templates that are available for you to
use that match your sort of financial

00:03:20.740 --> 00:03:23.409
use case and your technical use case.

00:03:23.890 --> 00:03:25.390
And you should just be able to say, yep.

00:03:25.540 --> 00:03:30.339
I run this on my cloud, uh, and
cool, like should be up and running.

00:03:30.850 --> 00:03:33.070
And we'll make sure that all
of the different services

00:03:33.370 --> 00:03:34.630
talk to each other properly.

00:03:35.130 --> 00:03:40.200
And yeah, basically hooks up the
front end and API off, maybe a.

00:03:40.440 --> 00:03:45.750
We're eventually going to set up like
storage and all of that kind of stuff

00:03:45.810 --> 00:03:49.380
that, that you might want out of a
modern web or mobile application.

00:03:50.220 --> 00:03:54.840
Um, Yeah, so that's, that's
kind of it right now.

00:03:54.840 --> 00:03:56.730
We're at the point where we can.

00:03:57.230 --> 00:04:01.279
We can sort of configure all of
the different components and we've

00:04:01.279 --> 00:04:04.010
got it set up where it's like, w w.

00:04:04.609 --> 00:04:08.000
Essentially, we're building a dependency
graph between these different things.

00:04:08.600 --> 00:04:10.250
Uh, installing them.

00:04:10.940 --> 00:04:15.589
And we have them sort of up and running
ish kind of a little bit locally.

00:04:16.070 --> 00:04:20.990
Um, I was talking to a buddy and he sort
of explained how it would make a lot of

00:04:20.990 --> 00:04:25.909
sense to use the same deployment tools
that we're using, uh, under the hood.

00:04:26.479 --> 00:04:32.599
Uh, to basically deploy to our development
environment in the same way that we would

00:04:32.599 --> 00:04:34.400
to a staging or production environment.

00:04:34.789 --> 00:04:37.909
So that kind of shifted my
way of thinking about things.

00:04:38.539 --> 00:04:41.960
Um, But yeah, that's,
that's kinda where we're at.

00:04:42.020 --> 00:04:46.130
We almost have it running in
development and I'm really excited.

00:04:46.219 --> 00:04:50.300
Um, I think it's, it's going to
be a really nice way to work.

00:04:50.719 --> 00:04:54.710
Uh, the core of a lot of
this is a tool called HASA.

00:04:55.430 --> 00:04:59.780
which makes it really, really,
really easy to build a graph QL

00:04:59.780 --> 00:05:02.510
API on top of a Postgres database.

00:05:03.080 --> 00:05:10.039
And my God, HASA is amazing and I've been
using it for a surprisingly long time.

00:05:10.159 --> 00:05:12.919
Uh, given how new it is.

00:05:13.280 --> 00:05:17.810
Uh, I think it may have only been out
for like a year when I started using it.

00:05:18.110 --> 00:05:22.430
Uh, back in 2019, but I
love this tool so much.

00:05:22.969 --> 00:05:30.530
Um, Yeah, so hacer is kind of the core and
we've got other things for like off and,

00:05:30.590 --> 00:05:35.330
uh, front end and to manage, uh, sort of.

00:05:35.960 --> 00:05:41.750
API requests that are not things that you
can do in a Hospira and storage object,

00:05:41.870 --> 00:05:44.090
storage, all kinds of stuff like that.

00:05:44.150 --> 00:05:47.240
It'll all be nicely packaged and
Hostra is kind of the core of it.

00:05:47.990 --> 00:05:51.320
Um, yeah, so basically we're
going to try and make it nice and

00:05:51.320 --> 00:05:56.000
easy to deploy Hostra and all of
the services you need around it.

00:05:56.210 --> 00:06:03.050
Uh, and that's the Chewy Stack and that's,
that is my update on the Chewy Stack.

00:06:03.380 --> 00:06:06.950
Um, I've also started doing live streams.

00:06:07.190 --> 00:06:08.900
Of me working on this thing.

00:06:09.650 --> 00:06:15.740
So whether you're a junior dev who wants
to see how, uh, how this kind of stuff

00:06:15.800 --> 00:06:20.479
is built, or you're a much more advanced
developer and you want to give me some

00:06:20.479 --> 00:06:22.580
advice, which I would greatly appreciate.

00:06:23.030 --> 00:06:26.990
Um, that would be, that would be
great if, uh, if any of you are

00:06:26.990 --> 00:06:30.620
interested and you want to get
involved and you think this project is

00:06:30.620 --> 00:06:33.229
neat, I would love to hear from you.

00:06:33.289 --> 00:06:35.810
I would love to collaborate with you.

00:06:36.140 --> 00:06:39.200
And hopefully we can get this
thing up and running soon.

00:06:39.260 --> 00:06:39.950
Hopefully.

00:06:40.190 --> 00:06:41.659
I think in the next couple of months,

00:06:42.409 --> 00:06:46.700
I think that's a, that's a good timeline
for a, definitely an MVB, not something

00:06:46.700 --> 00:06:51.200
that you're going to launch a production
grade app with, but, you know, Something.

00:06:51.699 --> 00:06:52.209
All right.

00:06:52.329 --> 00:06:53.049
See you folks.