AWS in Practice Industry Case: Microservices Deployment into AWS

1. AWS in SW Project
Industry case: Microservices Deployment into AWS
Anna Ruokonen / anna.ruokonen@gofore.com / 11.10.2019
11.10.2019

2. We change the world for the be1er through
digitalisa5on and by renewing ways of working

3. Gofore Oyj
Established 2001
Strongly growing company:
• Turnover 2018 n. 50 M€ (+49%)
• 558 professioanls (6/2019)
• 170+ clients
• Four acquisition (Leadin, Solinor,
Silver Planet, Mangodesign)
• Listed in First North 2017
2007-2014

4. We build the change with you
C LO U D
– ensure agile
development and light
maintenance.
L EA D
the digital change.
D ES I G N
new, user-oriented
digital services.
B U I L D
digital services and
service architecture of
the future .

5. Gofore infrastucture
Helsinki, Jyväskylä, München, Swansea, Tampere, Turku, Tallinn

6. Javascript/N
ode.js
29%
Java
23 %
C#
13 %
Python
13 %
Other
9 %
PHP
6 %
Scala
4 %
Kotlin
3 %
Clojure
1 %
BACKEND
React
46%
Other
24 %
Angular
13 %
Vue.js
8 %
Angular js
4 %
React
Native
3 %jQuery
3 %
React.js
1 %
JSP
1 %
FRONTEND
USEDTECHNOLOGIES MOBILEDEVELOPMENT PROJECTLENGTH
44% 33% 22%
11
%
11
%
React NaPve PWA Android Flutter iOS
DEVELOPERSPERTEAM
13%
52%
19%
16%
<3months
3 – 12m onths
1 – 3years
> 3years
27%
10%
46%
18%
LOCATIONOFWORK
At Gofore’s office &
rem otely
At client prem ises Com bination of
both
61% 19% 20%
LANGUAGEUSEDINPROJECT
FI EN
Finnish
68%
English
32%

7. CI /CDPLATFORMSINPROJECTS ABSTRACTIONLEVELFORINFRASTRUCTURE ORCHESTRATIONTECHNOLOGIESINPROJECTS
DEPLOYMENTFREQUENCY
44%
29%
13%
14%
3 – 12months > 3years
41% 33% 17% 9%
NOOFPROJECTSPERDEVELOPER
47% 25%
Jenkins VSTS
Circle
13%15% 3%
Travis
Bamboo
LOCATIONOFINFRAINPROJECTS
46% 33%
AWS Data
center
Azure
4%23% 1%
Google
cloud
Heroku
54%
50%
22%
8%
V i r t u a l M a c h i n e s
C o n t a i n e r s
S e r v e r l e s s
P h y s i c a l h a r d w a r e
Infrequently
Every few weeks
Weekly
Daily
29% 16%
Customscripts ECS
Kubernetes
11% 3%
Marathon
Docker
swarm
3%

8. Agenda
● AWS Cloud infrastructure and core services
● Microservices
● How to manage your cloud infrastructure?
● Industry case: Microservices Deployment into AWS

9. Regions and availability zones
The AWS Cloud spans 69 Availability Zones within 22 geographic Regions around the
world
● Performance
● Availability
● Security
● Reliability
● Scalability
● Low-Cost
hEps://aws.amazon.com/about-aws/global-infrastructure/

10. Simple Storage Service - S3
● Object storage
● Amazon S3 automatically scales to high request rates.
● Used to store and retrieve any amount of data (files)
● Data is stored as objects within resources called “buckets”, and a single object can
be up to 5 terabytes in size.
● Static website hosting
Other storages EBS, databases,..

11. Elas%c Compute Cloud - EC2
● Virtual machines
● Prizing: On-Demand, Reserved, and Spot
● Host type: Shared HW, Dedicated Host, and Dedicated Instance
● Amazon Machine Image
● Security Groups act as instance level firewall

12. Elastic Load Balancer - ELB
Application Load Balancer
● HTTP and HTTP
● Distributes incoming application traffic multiple targets
○ EC2 instance, container, IP, and Lambda
● Path-based routing
● SSL termination
● Authentication
● AWS WAF
Network Load Balancer
● TCP

13. Virtual Private Cloud - VPC
● Enables you to launch AWS resources into a virtual network that you've defined. Your
data center in the cloud.
● A subnet is a range of IP addresses in your VPC
● You define internet connecCvity: Private or Public subnet
● Network Access Control Lists (ACLs)
Use cases:
● Separate dev/test/prod: mulCple VPCs
● N-Cer architecture (mulCple subnets)

14. Databases
● Relational Databases
○ RDS - (MySQL, MariaDB, PostgreSQL, Oracle, and Microsoft SQL Server DB)
○ Aurora - serverless
● NoSQL
○ DynamoDB - serverless
○ DocumentDB

15. Microservices
● Applications composed of independent services that communicate over well-defined
APIs
● Autonomous
● Specialized
Containers
● Repeatable
● Self-contained execution environments
● Lightweight

16. Elastic Container Service (ECS)
● Orchestrates the execution of containers
● Maintains and scales the fleet of nodes running your containers
● Removes the complexity of standing up the infrastructure
Fargate
● Fully managed container service
● Provisioning and managing clusters
● Management of runtime environment
● Scaling

17. Elas%c Container Service (ECS)

18. Elas%c Kubernetes Service (EKS)
● Kubernetes is an open-source system for automa%ng deployment, scaling, and
management of containerized applica%ons
● Makes it easy to deploy, manage, and scale containerized applica%ons
● Amazon EKS runs the Kubernetes management infrastructure for you
● Amazon ECR for container images
● Elas%c Load Balancing for load distribu%on

19. Elastic Kubernetes Service (EKS)

20. Lambda
● Fully managed compute service
● Runs stateless code
● Supports Node.js, Java, Python, C# , Go, and Ruby
● Runs your code on a schedule or in response to events
● You are charged based on the number of requests for your functions and the
duration
● You can build Serverless microservices with Lambda
● Integrated with API Gateway: Serverless APIs
● Integrated with ALB

21. Infrastructure as a Code (IaaC)
Versioning, Code review
Cloudformation
● AWS solution
● manages the state for you
● JSON or YAML
Terraform
● 3rd party
● complex logic
● flexible

22. IaaC: Cloudforma-on example
Resources:
Ec2Instance:
Type: 'AWS::EC2::Instance'
Properties:
SecurityGroups:
- !Ref InstanceSecurityGroup
- MyExistingSecurityGroup
KeyName: mykey
ImageId: ami-7a11e213
InstanceSecurityGroup:
Type: 'AWS::EC2::SecurityGroup'
Properties:
GroupDescription: Enable SSH access via port 22
SecurityGroupIngress:
- IpProtocol: tcp
FromPort: '22'
ToPort: '22'
CidrIp: 0.0.0.0/0

23. CI/CD pipelines
AWS Tools
● Code Commit
● Code Build
● Code Deploy
● Elastic Container Registry (ECR)
Other tools
● GitLab CI/CD (https://docs.gitlab.com/ee/ci/README.html)
● Jenkins

24. Case: IIoT pla,orm - (Apps and Microservices)
API Gateway
Monitoring
Analytics Process
/devices /metadata
/processes
/performance
/customers
AWS Application Load Balancer
/users
/signalData

25. Case: IIoT pla,orm - (Apps and Microservices)
● GitLab CI/CD pipelines
● Microservices are deployed as Docker containers into Kubernetes cluster (EKS + EC2)
● Front-end applicaHons are deployed into S3 bucket
● Build pipeline and Deploy pipeline
● Dev/test deployment is automaHc
● ProducHon deployment needs manual trigger
● DownHme close to zero

26. Build
Review
Dev
Staging
Production
Deploy
Gitlab
Gitlab
CI/CD
S3/k8s
git
push
npm
registry
(nexus)
Docker
registry
(Gitlab)
automatic
manual
Pipeline Overview

27. GitLab CI/CD
● GitLab CI/CD is configured by a file called .gitlab-ci.yml placed at the
repository’s root
● The scripts set in this file are executed by the GitLab Runner
● GitLab CI/CD builds, tests, and deploys your applications to any AWS
infrastructure whether you are using EC2, ECS, or EKS.

28. CI/CD Pipeline Structure

29. CI/CD Pipeline Structure
analytics deploy_analy
tics

30. Front-end applica/ons - Serverless
● React and Angular applica/ons are deployed into S3 bucket
● Copy compiled bundle in S3 bucket
● Kubernetes handles incoming traffic
variables:
S3_BUCKET_NAME: "yourbucket"
build:
..
deploy:
image: python:latest
script:
- pip install awscli
- aws s3 cp ./dist s3://$S3_BUCKET_NAME/ --recursive
only:
- master

31. Microservices - EKS
● Microservices are deployed on EKS cluster
● Gitlab Pipeline: Build - Publish - Deploy
● Deployment.yaml
○ Replicas
○ Strategy (e.g. rolling, recreate, blue/green, canary)
○ Containers
○ Probes: readiness, healthy
● kubectl: kubectl apply -f deployment.yaml

32. apiVersion: apps/v1
kind: Deployment
metadata:
name: hello-world
spec:
replicas: 3
strategy:
type: RollingUpdate
rollingUpdate:
maxSurge: 1
maxUnavailable: 33%
deployment.yaml
template:
spec:
containers:
- name: hello
image: hello-world:<VERSION>
ports:
- containerPort: 8080
readinessProbe:
httpGet:
path: /healthy
port: 8080
initialDelaySeconds: 2
periodSeconds: 2

33. build:
...
publish:
...
deploy:
stage: deploy
image: helm-kubectl
script:
- kubectl config set-cluster k8s --server="${SERVER}"
- kubectl config set clusters.k8s.certificate-authority-data ${CERTIFICATE_AUTHORITY_DATA}
- kubectl config set-credentials gitlab --token="${USER_TOKEN}"
- kubectl config set-context default --cluster=k8s --user=gitlab
- kubectl config use-context default
- sed -i "s/<VERSION>/${CI_COMMIT_SHORT_SHA}/g" deployment.yaml
- kubectl apply -f deployment.yaml
.gitlab-ci.yml

34. Pipeline Philosophy
● Separation of concerns (build, deploy)
● Reusability (shared pipeline code)
● Build/Generate only once
● Aim for "internal open-source model" (e.g. shared npm packages)
● Aim for best practices and standard conventions used by open-source communities
(Javascript/Typescript)
(Aki Mäkinen, Gofore)

35. Thank You
Anna Ruokonen anna.ruokonen@gofore.com