Over the last lectures we switched
from our multi container set up
where we had our own MongoDB container
to this single container deployment
where we instead utilized MongoDB Atlas
for the database and I outlined why we did this
in the last lectures.
Now I wanna finalize our deployed application
and reach the final architecture for this application.
Because we must not forget that previously when we
learned about Docker Compose we had a backend
and a front end.
And I now brought back that front end,
you attached find this updated project
which is the project configuration we derived
up to this point.
So all to the Docker Compose file without MongoDB.
But now also again with the react front end
which renders this website
users will be able to interact with.
Now our final goal here will be to stick to
using MongoDB Atlas.
But of course now we don't just wanna have to
NodeJS REST API being deployed,
but we also wanna have a second container up and running
which holds our react single page application
so that users can reach that.
And then it's this single page application
talking to our NodeJS REST API.
And therefore I again wanna deploy a second container.
I wanna deploy this react single page application
to my ECS task so that we again have two containers there.
And that's there for what we're going to tackle next.
And it might sound very easy.
We did deploy a couple of containers already.
But this specific application
and applications like this react single page application
have their very own challenging element
which we have to understand and solve first
before we can deploy anything.
And that is that this application,
the react single page application,
and all similar applications,
front end web applications,
typically have a build step.
Which means we can't run them on the server
as we run them locally.
And here's why.