This document discusses using Docker Swarm to implement a microservices architecture. It provides an overview of the typical microservices architecture with separate containers for each service that communicate over a network. It then discusses some of the pros and cons of Docker Swarm, including its abilities around service discovery, logging, isolation, deployment and management. The document concludes with demonstrations of implementing the sample architecture using both Docker Compose and Docker Swarm.

1. Microservices with Docker Swarm
Alper Kanat <alper.kanat@commencis.com>

2. ● 1984, borned in İstanbul
● 2007, Işık University CSE
● 2007 - 2009 // Parkyeri
● 2010 - 2013 // Huawei, put.io, GROU.PS
● 2013 - 2014 // Butigo
● 2014 - 2018 // Monitise MEA
● 2018 - … // Commencis (formerly known as Monitise MEA)
● Solution Architect
● PHP, Python, nodejs, Java, Deployment, DevOps, AWS, GCP
● Web: http://alperkan.at
● Twitter: @tunix
● Medium: @tunix
About Me

3. ● Acquired Pozitron in 2014
● Acquired by Fiserv in 2017
● Continues as Commencis as of 2018
● Delivers mobile/web applications and end-to-end solutions
to banks, airlines, insurance and various other companies
world wide.
● Top 3 mobile software exporting company in Turkey
● 3 offices in İstanbul, İzmir and Dubai.
● Around 200 team members and technology experts
About Monitise MEA

4. About Monitise MEA

5. Before Microservices...

6. Typical Microservices Architecture

7. ● Docker and its ecosystem is not an answer for everything.
○ For on-prem scenario, there are various things to think about.
○ It’s sometimes better to manage external dependencies (ex: databases) the good old way.
○ Persistence is hard!
● Depending on the technology stack, you may need additional software & configuration.
○ How to handle service discovery? Via Docker, zookeeper, etcd, consul?
○ How to handle logging? ELK, collectd etc?
No silver bullet...

8. Pros
● Service Discovery
● Simple logging
● Isolation
● Declarative deployment & management
● Simple monitoring
● Rollback & failover
● Easy to make changes on runtime
Cons
● Learning curve
● Need for a proper pipeline setup
● Immature plugin ecosystem
● Some functionalities may need 3rd party
plugins
Pros & Cons

9. Demo Architecture with Compose

10. Demo Architecture with Swarm

11. Service Discovery

12. DEMOhttps://github.com/tunix/docker_izmir_keynote
Let’s pray to the demo gods…