Creating microservices architectures using node.js and Kubernetes

Slides for my talk at JSDayES 2017

Transcript

1. Creating microservices architectures using node.js and Kubernetes
2. CTO at seedtag Paul Goldbaum Who is this guy?! @paulgoldbaum
3. Our original stack Symfony 2 MongoDB Physical servers hosted at OVH PHP 5.6
6. Our current stack MongoDB + Google Datastore Kubernetes through Google Container Engine Node.js + Express Apache Spark
7. Don’t do it*
8. Why do we need a microservices platform?
9. Platform
10. Load Balancer Deployment manager Log handler Process supervisor Service discovery Service communication Storage manager
11. Abstract away differences between services Isolate apps from each other Reserve resources in shared execution environment Wrap as executable unit
12. Provides deployment, scaling and management of containerized applications Works on some of the main public and private cloud providers and on-premise Serves as a layer of abstraction over the infrastructure Container cluster manager built by Google after Borg
13. Putting services into production
14. var express = require('express'); var app = express(); app.get('/', function(req, res) { res.send('Hello World!'); }) app.listen(3000, function() { console.log('Application running on port 3000!'); })
15. apiVersion: extensions/v1beta1 kind: Deployment metadata: name: hello-world spec: replicas: 2 template: metadata: labels: app: hello-world spec: containers: - name: main image: hello-world:v1 kubectl create -f hello-world.yaml
16. kubectl set image deployment/hello-world main=hello-world:v2
17. var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello World!'); }) app.get('/status', function (req, res) { res.sendStatus(200); }) app.listen(3000, function() { console.log('Application running on port 3000!'); })
18. … spec: containers: - name: hello-world image: hello-world:v1 ports: - containerPort: 3000 readinessProbe: httpGet: path: /status port: 3000 periodSeconds: 5
19. Service B
21. … var ready = true; app.get('/status', function (req, res) { if (ready) { res.sendStatus(200); } else { res.sendStatus(500); } }) process.on('SIGTERM', function () { ready = false; setTimeout(function() { server.close(function () { process.exit(0); }); }, 10000); }); …
22. Choosing programming languages
23. Small services give us flexibility when choosing languages/frameworks
24. We can now use right tool for the right job but…
25. status endpoint / connection drain docker build test environment app instrumentation Custom NodeJS Microservices Framework … now what?
26. Creating a new microservice should be EASY
27. Communicating microservices
28. GET /users HTTP/1.1 App A App B ? Synchronous communication
29. Synchronous communication using Kubernetes services App A Service B App B App B App B
30. apiVersion: v1 kind: Service metadata: name: hello-world spec: ports: - port: 3000 targetPort: 3000 selector: app: hello-world
31. Synchronous communication using Kubernetes services App A Service B App B App B App B
32. Synchronous communication using Kubernetes services App A Service B App B App B App B Circuit Breaker
33. App A App B Message bus OMG LOL Asynchronous communication
34. Monitoring services
36. Prometheus Labels can be added to time series to allow grouping of data by any criteria Provides powerful query operators Allows to use queries to generate alerts Time-series database created by SoundCloud
37. ALERT my_request_rate IF sum(rate(http_requests_total{kubernetes_name=“hello-world”}[1m])) < 100 FOR 5m LABELS { severity = "urgent" }
38. Connects to many different backend such as Prometheus, Graphite, InfluxDB, Elasticsearch, … Great for having your stats up on a screen in the office Web-based dashboard creator for visualizing time-series and application metrics
40. kube-state-metrics node-exporter Feeding data into our system express-prom-bundle
41. Service A Service B Service C
42. Instrumented apps send spans to Zipkin Outgoing requests are marked with a correlation ID Zipkin joins spans from a single correlation ID together to form traces Distributed tracing system by Twitter
44. Measure everything! Microservices are hard, imply a lot more operations work Creating a custom microservices framework is key to agility Conclusions
45. careers@seedtag.com Do you want to help us change the world of online advertising. Join us! Thank you! Contact: paul.goldbaum@gmail.com - @paulgoldbaum