Presentation from OOW2018

1. Develop, Build, Deliver and
Run Microservices with
Containers in the Cloud
Eugene Fedorenko

2. About me
Eugene Fedorenko
Senior Architect
Flexagon
adfpractice-fedor.blogspot.com
@fisbudo

3. Agenda
•Microservices
•Containers
•Docker
•Build containers
•Kubernetes
•Deploy to the cloud
•OKE/AKS/GKE
•Serverless
•Build, Deploy and Test with functions

4. Start

5. Winter Olympics 2018

6. Dashboard microservice

7. Simple Development Lifecycle

8. Environments challenge
DEV TEST PROD

9. The Idea.
Virtual Machine

10. Container
•A lightweight, stand-alone, executable package of a piece of
software that includes everything needed to run it: code,
runtime, system tools, system libraries, settings.
•Containers share the host operating system rather than the
hardware directly
•Way more lightweight than a VM
•Docker is the most popular implementation

11. Docker Container Manager

12. Docker vs VM

13. Medal table microservice

14. Microservices
•An architecture pattern decomposing vertically a
monolith system into loosely coupled subsystems
(microservices). Nothing more. The pattern doesn't
dictate how it should be done technically.
•Just to highlight it: Microservices and Containers
are not the same and totally independent. You can
use Docker with a monolith app, and you can have
several microservices without using Docker at all.

15. Containers content
UI
• Alpine
• Nginx 1.10.2
• Jet app
– html, css, js
Middleware
• Ubuntu
• Java 1.8.0_171
• Tomcat 8.5
• ADF libraries
12.2.1
• ADF BC app (war)
Database
• Oracle Linux
• Oracle DB
11.2.0.2 XE
• DB schema with
dashboard tables

16. Build an image

17. FROM nginx:1.10.2-alpine
COPY web /usr/share/nginx/html
EXPOSE 80
Dockerfile

18. •Cloud based registry
– Public (free)
– Private
•Centralized resource for container images
•Docker CLI provides access to Docker Hub
– docker search, pull, login, push
Docker Hub

19. Simple Development Lifecycle

20. •Open Source platform (Google born)
•Orchestration engine for Ops
•A level of abstraction hiding the complexity of a hybrid
environment (prem/cloud)
•Configuration properties
•Load balancing
•Scalability
•Security
•Visibility
Kubernetes

21. • Cluster. Set of physical or VMs. Masters and workers.
• Node. Worker. Minion. A physical or virtual machine. Docker is installed on it.
• Kubelet. Internal service running on each worker node and managed by a master
node. Makes sure that everything works according to configuration files.
Kubernetes Architecture

22. • Kubectl. Kubernetes CLI.
• REST API.
• Dashboard.
Kubernetes Architecture

23. • Pod. Logical set of containers. A smallest deployable and scalable unit
• Replica set. Defines how many instances of a pod should be alive
• Deployment. Creates a Replica Set to bring up a desired number of Pods
Kubernetes Architecture

24. • Service. Logical set of pods with a stable ip/access rules and name. Has a
lightweight internal load balancer.
• Internal, External
Kubernetes Architecture

25. Microservice as a K8s application

26. Front End
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: olympics-dsh-fe
labels:
run: olympics-dsh-fe
spec:
replicas: 1
template:
metadata:
labels:
run: olympics-dsh-fe
spec:
containers:
- image: eugeneflexagon/olympics-dsh-fe:latest
imagePullPolicy: Always
name: olympics-dsh-fe
ports:
- containerPort: 80
protocol: TCP
apiVersion: v1
kind: Service
metadata:
name: olympics-dsh-fe-svc
spec:
selector:
run: olympics-dsh-fe
ports:
- port: 8088
targetPort: 80
type: ClusterIP

27. Middleware
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: olympics-dsh-mw
labels:
run: olympics-dsh-mw
spec:
replicas: 1
template:
metadata:
labels:
run: olympics-dsh-mw
spec:
containers:
- image: eugeneflexagon/olympics-dsh-mw:latest
env:
- name: OLYMPICS_DB_URL
value: "jdbc:oracle:thin:@olympics-dsh-db-svc:1521:XE"
name: olympics-dsh-mw
ports:
- containerPort: 8080
apiVersion: v1
kind: Service
metadata:
name: olympics-dsh-mw-svc
spec:
selector:
run: olympics-dsh-mw
ports:
- port: 8088
targetPort: 8080
type: ClusterIP

28. Database
apiVersion: apps/v1beta2
kind: StatefulSet
metadata:
name: olympics-dsh-db
labels:
run: olympics-dsh-db
spec:
selector:
matchLabels:
run: olympics-dsh-db
serviceName: "olympics-dsh-db-svc"
replicas: 1
template:
metadata:
labels:
run: olympics-dsh-db
spec:
containers:
- image: eugeneflexagon/olympics-dsh-db:latest
volumeMounts:
- mountPath: /u01/app/oracle/oradata
name: dsh-db
name: olympics-dsh-db
ports:
- containerPort: 1521
apiVersion: v1
kind: Service
metadata:
name: olympics-dsh-db-svc
spec:
selector:
run: olympics-dsh-db
ports:
- port: 1521
targetPort: 1521
clusterIP: None
volumeClaimTemplates:
- metadata:
name: dsh-db
spec:
accessModes: [ "ReadWriteOnce" ]
resources:
requests:
storage: 100M

29. Pods communication
<Resource name="jdbc/olympics-db-connDS"
auth="Container"
type="oracle.jdbc.pool.OracleDataSource"
factory="oracle.jdbc.pool.OracleDataSourceFactory"
url="${OLYMPICS_DB_URL}"
...
spec:
containers:
- image: eugeneflexagon/olympics-dsh-mw
env:
- name: OLYMPICS_DB_URL
value: "jdbc:oracle:thin:@olympics-dsh-db-svc:1521:XE"
imagePullPolicy: Always
name: olympics-dsh-mw

30. Ingress

31. Ingress
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: olympics-ing
annotations:
kubernetes.io/ingress.class: 'nginx'
nginx.ingress.kubernetes.io/rewrite-target: /
spec:
tls:
- secretName: tls-secret
rules:
- http:
paths:
- path: /javabackend-dsh
backend:
serviceName: olympics-dsh-mw-svc
servicePort: 8088
- path: /olympics-dsh
backend:
serviceName: olympics-dsh-fe-svc
servicePort: 8088

32. K8S clusters in the cloud

33. Kubectl
•K8s command line tool
•Configured with “config” file
– $HOME/.kube/config
•Can be configured for multiple clusters (contexts)
•Configuration is provider specific
kubectl config use-context aws
kubectl apply -f olympics-fe.yaml

34. Build & Deploy automation

35. Build & Deploy automation

36. Workflows as Function Flows

37. Serverless
• A unit of work consumes resources only when it is used
– Function is a unit of work
• stateless
• serves one goal
• arguments (input) and result (output)
• Orchestration of independent pieces of work (functions as a
service FaaS)
– Carrying state of the entire flow (program)
– Error handling
– Transaction management

38. Serverless
• Code centric paradigm. Hyde Infrastructure.
–Focus on coding resolving business problems and forget about
infrastructure
–Everything is working on some “computing resources”
• Scalability
–Developers don't do anything for scaling. Scaling is handled
automatically.
• Billing
–Don't pay for idle time
–Pay for milliseconds
• Utilization
–Many small pieces running for short time on same VM

39. Serverless Platforms
•AWS Lambda
•Azure Functions
•OpenWhisk
– Open Source / Apache
•Fn
– Open Source / Oracle
– container native
•OpenFaaS
– Open Source / Alex Ellis
– container native

40. Fn
• Fn components are Docker containers
• Requires only Docker engine
• Can run on Kubernetes cluster

41. Ojet Builder Container

42. Ojet Builder Function
curl http://localhost:8080/ojetbuilder /build -d “$GIT_URL
$NEXUS_URL $PROJECT_VERSION"

43. Q&A