Go to file
Torma Kristóf 06032d6b64
All checks were successful
continuous-integration/drone/push Build is passing
rename drone config
2020-05-09 23:03:21 +02:00
.github Update ISSUE_TEMPLATE 2017-05-04 13:30:48 -07:00
k8s-specifications Set an explicit username/password for Postgres in the swarm and k8s files too 2020-02-19 14:57:37 -05:00
result Set an explicit username/password for Postgres in the swarm and k8s files too 2020-02-19 14:57:37 -05:00
vote Update 'vote/Dockerfile' 2020-04-24 16:47:13 +02:00
worker Update 'worker/Dockerfile' 2020-04-24 17:26:49 +02:00
.drone.yml rename drone config 2020-05-09 23:03:21 +02:00
.gitignore ignore node_modules in git and docker build 2019-08-25 15:17:56 -04:00
architecture.png Update architecture diagram 2016-06-19 12:14:38 -07:00
docker-compose-javaworker.yml Set an explicit username/password for Postgres in the other Compose files too 2020-02-19 14:44:54 -05:00
docker-compose-k8s.yml Set an explicit username/password for Postgres in the other Compose files too 2020-02-19 14:44:54 -05:00
docker-compose-simple.yml Set an explicit username/password for Postgres in the other Compose files too 2020-02-19 14:44:54 -05:00
docker-compose-windows-1809.yml Add Windows 1809 support 2018-10-22 11:27:04 +01:00
docker-compose-windows.yml Pin to Nano Server SAC 2016 images 2018-09-26 19:41:20 +01:00
docker-compose.yml homework 2020-04-24 13:39:21 +02:00
docker-stack-simple.yml Set an explicit username/password for Postgres in the swarm and k8s files too 2020-02-19 14:57:37 -05:00
docker-stack-windows-1809.yml Add Windows 1809 support 2018-10-22 11:27:04 +01:00
docker-stack-windows.yml Pin to Nano Server SAC 2016 images 2018-09-26 19:41:20 +01:00
docker-stack.yml Set an explicit username/password for Postgres in the swarm and k8s files too 2020-02-19 14:57:37 -05:00
ExampleVotingApp.sln Add .NET Core 2.1 versions 2018-09-21 19:23:31 +01:00
Jenkinsfile Update Jenkinsfile 2018-08-16 23:45:13 +01:00
kube-deployment.yml Set an explicit username/password for Postgres in the swarm and k8s files too 2020-02-19 14:57:37 -05:00
LICENSE Add LICENSE and MAINTAINERS 2016-03-31 11:49:23 -07:00
MAINTAINERS Add Mano as a maintainer 2016-10-20 10:25:10 +02:00
README.md Fix typo in markdown 2018-10-31 14:53:32 -06:00

Example Voting App

A simple distributed application running across multiple Docker containers.

Getting started

Download Docker Desktop for Mac or Windows. Docker Compose will be automatically installed. On Linux, make sure you have the latest version of Compose.

Linux Containers

The Linux stack uses Python, Node.js, .NET Core (or optionally Java), with Redis for messaging and Postgres for storage.

If you're using Docker Desktop on Windows, you can run the Linux version by switching to Linux containers, or run the Windows containers version.

Run in this directory:

docker-compose up

The app will be running at http://localhost:5000, and the results will be at http://localhost:5001.

Alternately, if you want to run it on a Docker Swarm, first make sure you have a swarm. If you don't, run:

docker swarm init

Once you have your swarm, in this directory run:

docker stack deploy --compose-file docker-stack.yml vote

Windows Containers

An alternative version of the app uses Windows containers based on Nano Server. This stack runs on .NET Core, using NATS for messaging and TiDB for storage.

You can build from source using:

docker-compose -f docker-compose-windows.yml build

Then run the app using:

docker-compose -f docker-compose-windows.yml up -d

Or in a Windows swarm, run docker stack deploy -c docker-stack-windows.yml vote

The app will be running at http://localhost:5000, and the results will be at http://localhost:5001.

Run the app in Kubernetes

The folder k8s-specifications contains the yaml specifications of the Voting App's services.

First create the vote namespace

$ kubectl create namespace vote

Run the following command to create the deployments and services objects:

$ kubectl create -f k8s-specifications/
deployment "db" created
service "db" created
deployment "redis" created
service "redis" created
deployment "result" created
service "result" created
deployment "vote" created
service "vote" created
deployment "worker" created

The vote interface is then available on port 31000 on each host of the cluster, the result one is available on port 31001.

Architecture

Architecture diagram

Note

The voting application only accepts one vote per client. It does not register votes if a vote has already been submitted from a client.