Gain insights into working with Docker containers, discover common pitfalls, and explore best practices to efficiently build modern applications, regardless of your experience level.

A Guide For Building Modern Applications With Docker_ .png

vm.tar.gz

multi-container-app

run-todo-mvc

nodejs

python-fastapi

python-fastapi-copy

overriding-docker-compose-settings

overriding-docker-compose-settings-copy

docker-compose-override

This course simplifies working with Docker containers (whether you're a novice or an intermediate engineer) and also exposes some common pitfalls. We’ve also added some best practices that might be useful while working with Docker.

Simple Steps to Building Modern Applications with Docker

**BitLink** is a URL-shortening and link management application that takes a big URL and converts it into a new short URL that’s easy to share. A database is required for such an application to store and maintain a map of shortened URLs and their original URLs. A simple version of a URL-shortening application could have a microservice that generates shortened URLs and another microservice that displays the URL to the user  





Let’s refer to the services as `backend` and `frontend` services.

We use an existing codebase to create a multi-container application for this type of application.

If we haven’t cloned the project yet, we do so now on GitHub with the following command:



git clone https://github.com/abiodunjames/docker-lessons.git 




We then navigate to the `multi-container-app/exercise` directory in the following way:





There are two directories named `backend` and `frontend`. The `backend` directory contains the back-end code, which exposes the API for generating shortened URLs.
The front-end code—which is responsible for the user interface—is located in the `frontend` directory. There are a few prerequisites that must be met before we can run the applications with `docker-compose`.



*   Both the `backend` and `frontend` need to be containerized.
*   The `frontend` service should be able to access the APIs of the `backend` service. This means that the `frontend` service must be able to communicate with the `backend` service.
*   Since containers are transient, we need persistent storage—a database—to keep URLs.
*   The `backend` service should be able to connect to the database.




Learn to compose multi-container applications with docker-compose.

Introduction to the Course

Getting Started with Docker

A Guide to Building Docker Images

Working with Multiple Docker Containers

Working With Docker in CI Environments

Staying secure

Conclusion

Compose Multiple Applications