NB: This is very much a work in progress. Suggestions, constructive criticism, and (especially) PRs are most welcome!
Tested with Konvoy v1.2.1 and Kudo v0.7.5 on AWS.
This demo assumes you have kubectl
installed and connected to a Konvoy cluster running the default configuration in AWS.
Secondly, the commands below assume you have the kudo cli plugin installed.
brew install kudo-cli
or brew upgrade kudo-cli
- Nagivate to Grafana
- Hover over
+
in left-hand side nav bar - Select import
- Copy and paste JSON found here
- Click
Upload
- Select
Prometheus
as data source
kubectl kudo init
kubectl kudo install zookeeper --instance=zk
- Wait for all 3 Zookeeper pods to be
RUNNING
andREADY
kubectl kudo install kafka --instance=kafka
- Wait for all 3 Kafka brokers to be
RUNNING
andREADY
kubectl create -f https://raw.githubusercontent.com/kudobuilder/operators/master/repository/kafka/docs/v0.2/resources/service-monitor.yaml
kubectl apply -f https://raw.githubusercontent.com/tbaums/konvoy-kudo-studio/master/kafka-python-api/kafka-client-api.yaml
kubectl apply -f https://raw.githubusercontent.com/tbaums/konvoy-kudo-studio/master/svelte-ui/svelte-client.yaml
kubectl apply -f https://raw.githubusercontent.com/tbaums/konvoy-kudo-studio/master/kafka-node-js-api/kafka-node-js-api.yaml
- Visit <your AWS elb>/svelte
- Click 'Manufactoring & IoT' in the Nav bar
- Explain demo architecture
- Click '-' button to collapse architecture diagram
- Click button 'Click me to start fetch'
kubectl apply -f https://raw.githubusercontent.com/tbaums/konvoy-kudo-studio/master/kafka-dummy-actors/kafka-dummy-actor.yaml
- Observe a single actor on the map (left) and in the actor list (on right).
- Run
kubectl scale deploy kafka-dummy-actor --replicas=7
to see the list fill in real-time and observe the actors moving around the map.
- Click 'User Research' in the Nav bar
- Explain demo architecture
- Click '-' button to collapse architecture diagram
- Open browser 'Network' panel and reload the page. (Right click on the page, and select "Inspect Element". Then, select the 'Network' panel tab. Reload the page to start capturing network traffic.)
- Move mouse across left-hand screenshot
- Explain that each mouse movement captured by the browser is posted directly to the Python Kafka API server, via an endpoint exposed through Traefik
- Observe Node.js Kafka API reading from Kafka queue and returning the mouse movements in the right-hand screenshot
- Observe POST request duration (should be ~500ms)
To demonstrate the power of granular microservice scaling, first we need to generate more load on the Python Kafka API. We will then observe POST request times increase. Lastly, we will scale the Python Kafka API and observe POST request times return to normal.
From User Research screen (assumes above demo steps completed):
kubectl scale deploy kafka-dummy-actor --replicas=70
- Move mouse across left-hand panel
- Observe POST request duration in browser's Network panel (should be >1000ms)
kubectl scale deploy kafka-client-api --replicas=5
- Observe POST request duration (should return to ~500ms)