Introducción a los contenedores. Docker Introducción
- 2. Introduction If you needed to move an application from one environment to another, like from your laptop to the cloud, what challenges might you face? If you had to create an application that works in multiple environments, like a developer’s laptop, a testing server, and production, how would you approach it? What do you think a shipping container and a software container have in common? Have you heard of Docker or Kubernetes? What do you think they are used for?
- 3. What is a container? A ship? A virtual machine? A storage box for organizing ítems and storing data? A software packare?
- 4. Containers A container is a lightweight, standalone, and executable software package that includes everything needed to run a piece of software. This includes the application itself, along with all its dependencies, libraries, and configuration files. Containers are designed to run consistently across different computing environments, regardless of the underlying system or hardware.
- 5. Basic Components of Containers Engine/Client: Software that runs and manages containers (e.g., Docker Engine). Runtime: The tool that executes containers. Registry: A storage location for images (e.g., Docker Hub).
- 6. Continuous Integration Continuous integration is the practice of integrating source code changes frequently and ensuring that the integrated codebase is in a workable state.
- 7. Development Lifecycle Steps in containerized development: Build: "Create container images using tools like Dockerfiles." Test: "Run the containers in a test environment." Deploy: "Deploy containers to production using tools like Kubernetes."
- 8. Microservices Containers virtualize multiple application runtime environments on the same operating system instance, providing isolation and portability. Containerized microservices offer reduced overhead, increased portability, faster application development, and easier adoption of a microservices architecture. Containers make microservices scalable, isolated, and easier to manage, as each microservice runs in its own container.
- 9. Key Concepts Container: A small, portable box that runs an app with everything it needs to work. Image: A template used to create containers. Volume: Storage that keeps data safe even after the container stops. Container Components: Engine: The tool that runs the container. Runtime: The part that keeps the container running. Registry: A place to store and share container images Continous Integration: Frequently testing and combining code to ensure it works correctly. Containerized Development: Build: Create a container. Test: Check that the app works. Deploy: Launch the container to use it Microservices: Breaking an app into smaller, independent pieces that run in containers.