https://github.com/freyamade/netsoc-docker-talk
netsoc docker talk 2019
https://github.com/freyamade/netsoc-docker-talk
containers docker tech-talks ucc-netsoc
Last synced: 5 months ago
JSON representation
netsoc docker talk 2019
- Host: GitHub
- URL: https://github.com/freyamade/netsoc-docker-talk
- Owner: freyamade
- Created: 2017-10-14T13:57:59.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2022-12-07T17:46:30.000Z (over 3 years ago)
- Last Synced: 2024-10-18T23:17:32.532Z (over 1 year ago)
- Topics: containers, docker, tech-talks, ucc-netsoc
- Language: HTML
- Homepage: http://freyamade.netsoc.co/techtalks/docker
- Size: 3.53 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Docker

Docker is probably the most used containerisation platforms in the market at the moment?
What's a container I hear you say, and by coming to this talk you'll hopefully end up learning about what they are and why you should use it.
It's more a tool used in industry for deployment of applications but with the soon coming NetSoc Containers-as-a-Service platform you will soon be able to host your own applications in containers, and then you'll never look back.
## Roadmap
The talk will go as follows;
1. Brief Introduction
- What is a container
- Containers vs VMs
2. Getting started with Docker
- Images vs Containers
- Let's make a basic image
- Using Apache Docker image for development
3. Case Study of CIX
- The dark ages of VMs
- Issues regarding dependencies
- Old deploy scripts didn't / don't properly update dependencies
- Monolithic / Microservice
- Old code all on single server
- New stuff being deployed on multiple servers for load balancing / failover
- Stupid issues
- Server clock discrepencies causing issues with tokens >.>
- The new age of Docker / Kubernetes
- Dependencies are handled when building the image, not after deploying code
- Once image is built, that's all that has to be deployed
- Kubernetes clusters allow for load balancing, automatic rollout of upgrades to prevent downtime, failover etc
4. Conclusion