Scribd
Upload
37 views6 pages

SIT722-3.1 Task

Uploaded by

noumankhalid2410
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
37 views6 pages

SIT722-3.1 Task

Uploaded by

noumankhalid2410
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

3.

1P: Docker Compose Example


A screenshot of your VS Code console executing the appropriate git clone
https://github.com/bootstrapping-microservices-2nd-edition/chapter◻ 4.git command to obtain
a copy of the source code folder (chapter-4 ).

A screenshot showing the console with the output from the docker-compose -- version
command displayed.
A screenshot showing the console with the output from the docker-compose up -d –build
command displayed.
A screenshot showing the output from the docker-compose ps command displaying the
executing contain

A screenshot of the browser displaying the streame


A screenshot showing the console with the output from the docker-compose down
command displayed
Answers to the following questions:
Describe in your own words what each of the lines in the docker◻ compose.yaml do?
Docker Compose uses the docker-compose.yaml file as a configuration file to define and execute
multi-container Docker applications. Which version of the Docker Compose syntax is being
utilized is indicated by the version line. Every service that comprises the application is defined
under the services section. Every service has a name and has the ability to have different
configuration settings. The build section gives instructions on how to build the image from a
Dockerfile, while the image specifies the Docker image to use for the service. External access is
made possible by mapping ports from the host computer to the container using the ports section.
Data exchange and persistence are made possible by mounting directories from the host to the
container using the volumes section. The depends_on section determines the sequence in which
services should start, guaranteeing that dependent services are available, while the environment
section establishes environment variables within the container. Every line in the docker-
compose.yaml file instructs Docker on how to configure and link the different parts of the
application.

What is the difference between a .json and .yaml file?


Both YAML (.yaml) and JSON (.json) file formats are used for data representation and
configuration, however they differ greatly from one another. JSON defines objects and key-value
pairs using a syntax that uses curly brackets ({}) and colons. Strict formatting is required, with
commas between elements and quotes surrounding keys. Because this format is compatible with
JavaScript, it is frequently used in web development and APIs. Nevertheless, JSON is less
understandable by humans due to its verbosity. YAML, on the other hand, offers a more flexible
and forgiving style without the need for commas or quotes by representing structure and key-
value pairs using indentation and colons. As a result, editing YAML by hand is simpler and more
readable by humans. Because of this, YAML is frequently chosen for configuration files in
containerization and DevOps, where clarity is important.
Can docker-compose be used to support the deployment of an application to production
It is possible to deploy applications to production using docker-compose, but there are some
things to bear in mind. With Docker Compose, managing the entire stack with a single command
makes orchestrating multi-container applications easier. Small to medium-sized applications can
benefit from its ease service management and scaling. Furthermore, Docker Compose may be
integrated with Docker Swarm to enable more reliable production deployments with services like
service discovery and load balancing. On the other hand, Docker Compose might not have all of
the sophisticated capabilities and scalability possibilities that Kubernetes and other orchestration
technologies have. More complex or large-scale applications may require more advanced
deployment techniques. In many situations, Docker Compose is still a useful tool for managing
production deployments in spite of these drawbacks.
Compare the docker-compose.yaml in example-1 folder and the docker◻ compose.yaml in
example-2 . What is different and why?
Differences between the docker-compose.yaml files in the example-1 and example-2 folders
typically indicate the unique needs and development of each application. Example-1's file might
specify a more straightforward configuration with fewer services, whereas example-2's file might
specify more services, signifying a more intricate application. Variations in the build instructions
may indicate differences in the Docker image construction process, maybe due to the use of
alternative build contexts or Dockerfiles. To accommodate different networking requirements or
needs for data durability, the configurations of the ports and volumes may vary. Different
configurations or dependencies between services may be highlighted by variations in
environment variables. Various service start orders or dependency management approaches may
be suggested by changes made to depends_on or other orchestration settings. These variations
frequently result from the desire to enhance functionality, improve speed, or cater to particular
needs that were discovered following example-1's initial setup. The actual contents of these
docker-compose.yaml files would be required to give a more accurate comparison.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy