An example of two microservice architectures: a synchronous, coupled request/response approach and an asynchronous, less-coupled event-driven approach.
For more:
- 📃 Read the corresponding blog post/talk for more detail on why/how this exists
- 📺 Watch the video walkthrough of this demo to see how it works
- Tools needed to run this whole thing
- Bazelisk for the Go backend
- Minikube setup for the events broker
- Frontend tools for the webapp
- How to build and run
- Clean up and destroy everything
Set up bazelisk:
brew tap bazelbuild/tap
brew install bazeliskVerify that bazel points to bazelisk:
$ which bazel
/usr/local/bin/bazel
melinda at mmbp in ~/events on ml-add-bazel*
$ ls -l /usr/local/bin/bazel
lrwxr-xr-x 1 melinda admin 34 May 11 11:33 /usr/local/bin/bazel -> ../Cellar/bazelisk/1.6.1/bin/bazelInstall minikube, make Hyperkit the default driver, and give it more than the default amount of RAM:
brew install minikube
minikube config set driver hyperkit
minikube config set memory 2048 # 2 GBTo start minikube:
minikube startTo stop minikube:
minikube stopInstall Yarn and Node if you don't have them.
Then install the dependencies for the frontend app:
# from the js/ directory
yarn installThis deploys a clean version (nothing specific to this demo) of Kafka and Zookeeper to Kubernetes.
kubectl apply -f deployments/kafka.yamlkubectl exec -it kafka-0 -- bash
# from kafka/local/topics.sh
/opt/kafka/bin/kafka-topics.sh --create --partitions 2 --replication-factor 1 --zookeeper zookeeper:2181 --topic order.orderbazel run //go/services/order-sync:apibazel run //go/services/payment:apibazel run //go/services/delivery:apibazel run //go/services/order-async:apibazel run //go/workers/payment:workerbazel run //go/workers/delivery:workerTo build the breakfast-webapp app:
# from the js/ directory
yarn buildTo actually serve the breakfast-webapp app (won't work unless you build first):
# from the js/ directory
yarn startminikube delete