Swift Cloud Workshop - Swift Microservices

Deploying Swift 
With Docker and Kubernetes
Swift Cloud Workshop 3 
February 23rd, 2018
Chris Bailey 
(@Chris__Bailey)

: Key Technologies
Container Orchestration

: Key Technologies
Package and Deploy

: Key Technologies
MonitoringPackage and Deploy

: Key Technologies
Monitoring Fault TolerancePackage and Deploy

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Sources/Application/Application.swift
Tests/*
Package.swift
README.md
.gitignore
Kitura

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Tests/*
Package.swift
README.md
.gitignore
Kitura
import Kitura
import LoggerAPI
import CloudEnvironment
import KituraContracts
import Health
public let projectPath = ConfigurationManager.BasePath.project.path
public let health = Health()
public class App {
let router = Router()
let cloudEnv = CloudEnv()
public init() throws {
}
func postInit() throws {
initializeMetrics(app: self)
initializeHealthRoutes(app: self)
}
public func run() throws {
try postInit()
Kitura.addHTTPServer(onPort: cloudEnv.port, with: router)
Kitura.run()
}
}

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Tests/*
Package.swift
README.md
.gitignore
Dockerfile
Dockerfile-tools
.dockerignore

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Tests/*
Package.swift
README.md
.gitignore
Dockerfile
Dockerfile-tools
.dockerignore
FROM ibmcom/swift-ubuntu-runtime:4.0
# We can replace this port with what the user wants
EXPOSE 8080
# Install system level packages
# RUN apt-get update && apt-get dist-upgrade -y
# Add utils files
ADD https://raw.githubusercontent.com/IBM-Swift/swift-ubuntu-
docker/master/utils/run-utils.sh /swift-utils/run-utils.sh
ADD https://raw.githubusercontent.com/IBM-Swift/swift-ubuntu-
docker/master/utils/common-utils.sh /swift-utils/common-utils.sh
RUN chmod -R 555 /swift-utils
# Bundle application source & binaries
COPY . /swift-project
# Command to start Swift application
CMD [ "sh", "-c", "cd /swift-project && .build-ubuntu/release/
helium" ]

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Tests/*
Package.swift
README.md
.gitignore
Dockerfile
Dockerfile-tools
.dockerignore
Dockerfile
Dockerfile-tools

$ docker build -t <your username>/swift-app .

$ docker build -t <your username>/swift-app . 
$ docker run -p 49160:8080 -d <your username>/swift-app

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Tests/*
Package.swift
README.md
.gitignore
Dockerfile
Dockerfile-tools
.dockerignore
chart/swift-app/Chart.yaml
chart/swift-app/templates/deployment.yaml
chart/swift-app/templates/hpa.yaml
chart/swift-app/templates/service.yaml
chart/swift-app/values.yaml
HELM CHARTS

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Tests/*
Package.swift
README.md
.gitignore
Dockerfile
Dockerfile-tools
.dockerignore
HELM CHARTS
apiVersion: v1
description: A Helm chart for Kubernetes
name: swift-app
version: 1.0.0

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Tests/*
Package.swift
README.md
.gitignore
Dockerfile
Dockerfile-tools
.dockerignore
HELM CHARTS
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: “{{ .Chart.Name }}-deployment"
labels:
chart: “{{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}’
spec:
replicas: “{{ .Values.replicaCount }}”
revisionHistoryLimit: “{{ .Values.revisionHistoryLimit }}”
template:
metadata:
labels:
app: “{{ .Chart.Name }}-selector"
version: "current"
spec:
containers:
- name: “{{ .Chart.Name }}”
image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
imagePullPolicy: Always
livenessProbe:
httpGet:
path: /health
port: {{ .Values.service.servicePort }}
initialDelaySeconds:
{{.Values.livenessProbe.initialDelaySeconds}}
periodSeconds: {{ .Values.livenessProbe.periodSeconds}}
resources:
requests:
cpu: "{{ .Values.image.resources.requests.cpu }}"
memory: "{{ .Values.image.resources.requests.memory }}"
env:
- name: PORT

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Tests/*
Package.swift
README.md
.gitignore
Dockerfile
Dockerfile-tools
.dockerignore
HELM CHARTS
apiVersion: autoscaling/v2beta1
kind: HorizontalPodAutoscaler
metadata:
name: "{{ .Chart.Name }}-hpa-policy"
namespace: default
spec:
scaleTargetRef:
apiVersion: apps/v1beta1
kind: Deployment
name: "{{ .Chart.Name }}-deployment"
minReplicas: {{ .Values.hpa.minReplicas }}
maxReplicas: {{ .Values.hpa.maxReplicas }}
metrics:
- type: Resource
resource:
name: cpu
targetAverageUtilization:
{{.Values.hpa.metrics.cpu.targetAverageUtilization}}
- type: Resource
resource:
name: memory
targetAverageUtilization:
{{.Values.hpa.metrics.memory.targetAverageUtilization}}
{{ end }}

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Tests/*
Package.swift
README.md
.gitignore
Dockerfile
Dockerfile-tools
.dockerignore
HELM CHARTS
apiVersion: v1
kind: Service
metadata:
annotations:
prometheus.io/scrape: 'true'
name: "{{ .Chart.Name }}-service"
labels:
chart: "{{ .Chart.Name }}-{{ .Chart.Version | replace "+"
"_" }}"
spec:
type: {{ .Values.service.type }}
ports:
- name: http
port: {{ .Values.service.servicePort }}
selector:
app: "{{ .Chart.Name }}-selector"

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Tests/*
Package.swift
README.md
.gitignore
Dockerfile
Dockerfile-tools
.dockerignore
HELM CHARTS
replicaCount: 1
revisionHistoryLimit: 1
image:
repository: registry.ng.bluemix.net/replace-namespace/swift-app
tag: v1.0.0
pullPolicy: Always
resources:
requests:
cpu: 200m
memory: 300Mi
livenessProbe:
initialDelaySeconds: 3000
periodSeconds: 1000
service:
name: Node
type: NodePort
servicePort: 8080
hpa:
enabled: false
minReplicas: 1
maxReplicas: 2
metrics:
cpu:
targetAverageUtilization: 70
memory:
targetAverageUtilization: 70
services:
base:
enabled: false
replicaCount: 1
image:
tag : v0.9.9
weight: 100
prometheus:
enabled: false

$ helm package ./chart/swift-app

$ helm package ./chart/swift-app
$ helm install ./swift-app-1.0.0.tgz

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Tests/*
Package.swift
README.md
.gitignore
Dockerfile
Dockerfile-tools
.dockerignore
Jenkinsfile

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Tests/*
Package.swift
README.md
.gitignore
Dockerfile
Dockerfile-tools
.dockerignore
Jenkinsfile
#!groovy
@Library('MicroserviceBuilder') _
microserviceBuilderPipeline {
image = ‘swift-app’
}

Integrating with 
Kubernetes

• Checks status of service
• Requires /health endpoint providing data 
• Restarts service if not 200 OK
• Restarts service if no response 
Microservice Health: Liveness Probes

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Sources/Application/Routes/Health.swift
Tests/*
Package.swift
README.md
.gitignore
Kitura
import LoggerAPI
func initializeHealthRoutes(app: App) {
app.router.get("/health") { request, response, _ in
let result = health.status.toSimpleDictionary()
if health.status.state == .UP {
try response.send(json: result).end()
} else {
try response.status(.serviceUnavailable).send(json:
result).end()
}
}
}

• Provides “fault tolerance” to an application 
• Enables handling of failed downstream services
• Prevents repeated calls to failed services
• Provides alternative fallback function 
• Integrates with monitoring
Microservice Resilience: Hystrix and CircuitBreaker

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Sources/Application/Routes/Health.swift 
Tests/*
Package.swift
README.md
.gitignore
Kitura
breaker = CircuitBreaker(
name: "breaker", 
timeout: 10000,
maxFailures: 3,
rollingWindow: 60000,
command: myCommand,
fallback: myFallback)
func myFallback(err: BreakerError, msg: String) {
Log.verbose("Error: (error)")
Log.verbose("Message: (msg)")
}
func myCommand(invocation: Invocation<(String), String>) { 
 
}
breaker.run(commandArgs: , fallbackArgs:)
CircuitBreaker

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Tests/*
Package.swift
README.md
.gitignore
Kitura
let circuitParameters = CircuitParameters(
timeout: 2000,
maxFailures: 2,
fallback: myFallback)
let request = RestRequest(method: .get, url: "/hello")
request.circuitParameters = circuitParameters
SwiftyRequest

• Collects data from each enabled service 
• Requires /metrics endpoint providing data 
• Provides storage and correlation capabilities
• Provide customisable dashboard 
• Integrates with Graphana, Graphite, etc
Microservice Metrics: Prometheus

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Tests/*
Package.swift
README.md
.gitignore
Kitura
import Kitura
import LoggerAPI
import CloudEnvironment
import KituraContracts
import Health
public let projectPath = ConfigurationManager.BasePath.project.path
public let health = Health()
public class App {
let router = Router()
let cloudEnv = CloudEnv()
public init() throws {
}
func postInit() throws {
initializeMetrics(app: self)
initializeHealthRoutes(app: self)
}
public func run() throws {
try postInit()
Kitura.addHTTPServer(onPort: cloudEnv.port, with: router)
Kitura.run()
}
}

func add(_ a: Int,
to b: Int) -> Void
{
print(a + b)
}
let a = ”5”
let b = 3
Sources/*
Sources/Application/Routes/Health.swift
Sources/Applicaton/Metrics.swift
Tests/*
Package.swift
README.md
.gitignore
Kitura
import Kitura
import SwiftMetrics
import SwiftMetricsDash
import SwiftMetricsPrometheus
import LoggerAPI
var swiftMetrics: SwiftMetrics?
var swiftMetricsDash: SwiftMetricsDash?
var swiftMetricsPrometheus: SwiftMetricsPrometheus?
func initializeMetrics(router: Router) {
do {
let metrics = try SwiftMetrics()
let dashboard = try SwiftMetricsDash(swiftMetricsInstance:
metrics, endpoint: router)
let prometheus = try
SwiftMetricsPrometheus(swiftMetricsInstance:
metrics, endpoint: router)
swiftMetrics = metrics
swiftMetricsDash = dashboard
swiftMetricsPrometheus = prometheus
Log.info("Initialized metrics.")
} catch {
Log.warning("Failed to initialize metrics: (error)")
}
}

• ‘SwiftMetricsDash’ provides self-hosted monitoring 
• Inbound and Outbound request performance
• Resource monitoring
• ++ Dispatch queue monitoring 
• ++ profiling and flame graphs
Deep Analysis: ‘SwiftMetricsDash’

Config Fault Tolerance Health Check Health Metrics JWT Propagation
externalize configuration
to improve portability
build robust behavior to
cope with unexpected
failures
common format to
determine service
availability
common REST
endpoints for monitoring
service health
interoperable
authentication and role-
based access control

failures
common format to
determine service
availability
common REST
service health
interoperable
CloudEnvironment CircuitBreaker Health SwiftMetricsPrometheus Swift-JWT

failures
common format to
determine service
availability
common REST
service health
interoperable
CloudEnvironment CircuitBreaker Health SwiftMetricsPrometheus Swift-JWT
ibm-cloud-env hystrix-js /health appmetrics-prometheus jsonwebtoken

59
IBM Foundation
Support for Runtimes
generator-nodeserver
appmetrics monitoring
generator-swiftserver
swiftmetrics monitoringjavametrics monitoring
IBM Support for Runtimes
Enterprise Support: Runtimes

60
LoopBack
IBM Foundation
IBM Advanced
Support for Runtime
Frameworks
Enterprise Support: Frameworks

61
LoopBack
IBM Foundation
IBM Advanced
Support for Runtime
Frameworks
Enterprise Support: Module Ecosystems

PUBLIC NETWORK CLOUD NETWORK
CATALOG
ORDER
INVENTORY
USER
MySQL
MongoDB
SPARK
ELASTICSEARCH
BACKEND FOR 
FRONTEND
MICROSERVICES SERVICES
LOAD 
BALANCER

BROWSER
LOAD BALANCER
WEB BFF
TIME

BROWSER
LOAD BALANCER
WEB BFF
ORDER SERVICE
TIME

BROWSER
LOAD BALANCER
WEB BFF
ORDER SERVICE
MongoDB
TIME

BROWSER
LOAD BALANCER
WEB BFF
ORDER SERVICE
MongoDB
INVENTORY SERVICE
TIME

MySQL
BROWSER
LOAD BALANCER
WEB BFF
ORDER SERVICE
MongoDB
INVENTORY SERVICE
TIME

MySQL
BROWSER
LOAD BALANCER
WEB BFF
ORDER SERVICE
MongoDB
INVENTORY SERVICE
MongoDB
TIME

• Collects data from each enabled service 
• Propagates correlation ID using HTTP headers 
• Provides sampling, tracing, and debug capabilities
• Collects microsecond timestamps 
• Correlates data in Zipkin server
• Presents data in Zipkin dashboard
Request Tracking: OpenTracing and Zipkin

Swift Cloud Workshop - Swift Microservices

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Swift Cloud Workshop - Swift Microservices

Similar to Swift Cloud Workshop - Swift Microservices (20)

More from Chris Bailey

More from Chris Bailey (20)

Recently uploaded

Recently uploaded (20)

Swift Cloud Workshop - Swift Microservices