Microservices with Docker Swarm and Consul
•Télécharger en tant que PPTX, PDF•
4 j'aime•1,123 vues
This document discusses implementing microservices using Docker Swarm and Consul. It recommends programming languages and tools for orchestration, databases, load balancing, monitoring, and other functions. Docker Swarm allows clustering Docker hosts into a pool of resources. Consul provides service discovery, configuration, and failure detection across multiple datacenters. Consul-Template listens for Consul updates and configures applications. Registrator automatically registers and deregisters Docker services with Consul. An example scenario shows how services scale across nodes with this architecture.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (10)
Similaire à Microservices with Docker Swarm and Consul
Similaire à Microservices with Docker Swarm and Consul (20)
Dernier
Dernier (20)
Microservices with Docker Swarm and Consul
- 1. Microservices with Docker Swarm and Consul
- 3. Agenda - Something about Microservices - Implement Microservices with Docker Swarm and Consul
- 9. “You shouldn't start a new project with microservices, even if you're sure your application will be big enough to make it worthwhile” (Martin Fowler)
- 11. Some Suggestions Programing: Python, NodeJS, Golang* Orchestration: Docker, Docker Swarm, Consul, Consul-Template, Registrator, CoreOS* Databases & Caches: PosgreSQL, Cassanda, ElasticSearch, Redis Load Balancer & API Gateway: Nginx Queues: Kafka CI/CD: Jenkins, Ansible Monitors: Grafana + InfluxDB + (CollectD, cAdvisor) Logs: Kibana + ElasticSearch + FluentD Data Center: AWS EC2, AWS S3, AWS Float IP, Cloudfront CDN & DNS & DDOS Protection: Cloudflare Documents: Swagger, Markdown, mkdocs
- 13. An Example Node Gateway will be used a API Gateway and Load Balancer Node Agent One, Node Agent Two will be used to run services that are able to scale.
- 14. Docker & Docker Swarm Docker is a platform for developers and sysadmins to develop, ship, and run applications. Docker lets you quickly assemble applications from components and eliminates the friction that can come when shipping code. Docker lets you get your code tested and deployed into production as fast as possible. Docker Swarm is native clustering for Docker. It allows you create and access to a pool of Docker hosts using the full suite of Docker tools. Because Docker Swarm serves the standard Docker API, any tool that already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts #install $ docker pull swarm #run joiner $ docker run -d swarm join -- addr=172.20.20.11:2375 token://acdb9dfa3ea6da0b0cfb2c819385fcd3 #run manager $ docker run -d -p 12375:2375 swarm manage token://acdb9dfa3ea6da0b0cfb2c819385fcd3
- 15. Consul and Consul-Template Consul - Service Discovery - Key/Value Storage - Failure Detection - Multiple Datacenter Consul-Template - Listen/Query the updates from Consul - Updates Configuration File by the templates provided #run a consul agent $ consul agent -data-dir /tmp/consul -node=agent-one -bind=172.20.20.11 -client=0.0.0.0 -config-dir /etc/consul.d -retry-join 172.20.20.10 #run consul-template exec consul-template -consul 127.0.0.1:8500 -template "/build/gateway/consul- template/nginx.ctmpl:/etc/nginx/sites- available/default:service nginx reload" -retry 30s
- 16. Registrator Registrator automatically registers and deregisters services for any Docker container by inspecting containers as they come online. Registrator supports pluggable service registries, which currently includes Consul, etcd and SkyDNS 2. #run registrator $ docker run -d --name=registrator --net=host -- volume=/var/run/docker.sock:/tmp/docker.sock gliderlabs/registrator:latest consul://localhost:8500
- 17. A Scenario At the beginning, Service #1 only runs in Node 2. After that Service #1 scales to Node 2 Via Docker API, Registrator will know the appearance of Service #1 on Node 2. Registrator will register Service #1 with Consul. In the meanwhile, Consul-Template in listening Consul. So Consul-Template will know the new service is up in Node 2. Finally, Consul-Template will trigger a reload command to Nginx add the new service into load balancer.