1.
Serverless Computing -
Run Code, not Servers
Nils Rhode
Team & Tech Lead @ Haufe.Group

2.
From Monolith to Serverless

3.
From monolith to serverless

4.
From monolith to serverless
Focus on business logic
Levelofabstraction
• Deploy in weeks
• High maintenance
• Limited scaling & “guess“ planing
• Faster provisioning
• Reduced maintenance
• More scale & flexible resources
• Fast & Easy Deployment
• Higher resource utilization
• Platform independent
Physical server
VMs
Containers
Serverless
• Deploy in seconds
• Continous scaling
• Zero Maintenance &
pay per usage

5.
From monolith to serverless
No servers to provision
or manage
Scales automatically
with usage
Built-in availability
and fault tolerance Never pay for idle

6.
Serverless Architectural Pattern

7.
Data processing

8.
Serverless Architectural Pattern
Data
Processing

9.
Web application

10.
Serverless Architectural Pattern
Data
processing
Web
Applications

11.
Serverless Architectural Pattern
Web
Applications
Backends
IT
Automation
Data
Processing

12.
Data Processing:
Haufe Redaktionssystem (HRS)

13.
Haufe Redaktionssystem (HRS)
• In-house developed CMS (20 years old)
• Based on old technologies
• (Zope, Python2, Oracle…)
• Large monolith with different subcomponents
• Import, processing, export of content
• Many work aids for the editors & authors
HRS
Artikel-
box
Docu-
ments
Autoren
Tool
EDB
XMetal
Lauf-
listen
Autoren
DB
Normen
DB
Toolbox
Medien
DB
Stichwort
DB

14.
Entscheidungsdatenbank (EDB)
• HRS component for court decision
• 500.000 court decision
• 40.000 judgment commenteries
• 20.000 lawsuits
• More than 1.4 Mio. Citiazitions
• Oldest component of the HRS Monolith
• Technology components:
• Backend: Oracle 11 + Python2 + Perl
• Frontend: MS Access XP
• Workflows: Perl Skripten + Office 2010 VB macros
• Complex import and export workflows
HRS
Artikel-
box
Docu-
ments
Autoren
Tool
EDB
XMetal
Lauf-
listen
Autoren
DB
Normen
DB
Toolbox
Medien
DB
Stichwort
DB

15.
Data Processing:
EDB Architecture

16.
Re-Engineering of the HRS
• Breaking down the monolith
• First component to replace: EDB
• Future-proof: Use of state-of-the-art technology
• Low maintenance effort: use of services
• Fast and affordable workflows: Process millions of documents

17.
Overview of EDB Architecture

18.
Serverless Workflow

19.
Event Trigger
API Call via API Gateway
S3 Event Trigger
Cronjobs (via CloudWatch Events)
SQS (Message Queue)
RDS Database (Aurora)

20.
Serverless Development

21.
Serverless Development

22.
Serverless Development

23.
Serverless Development

24.
Serverless Development

25.
Serverless Orchestration

26.
Serverless Orchestration

27.
Serverless Orchestration

28.
Serverless Orchestration
Next step based on choice

29.
Serverless Orchestration
Steps in Parallel

30.
Serverless Orchestration

31.
Benefits of Serverless
• Cost savings (Never pay for idle)
• 10 imports per month with 1,000 to 10,000 files each - as fast as possible (scalability)
$79,65
$42,92
$0,89
$4,52
$0,97
16 X T2.NANO 1 X T2.MEDIUM 16 LAMBDAS
Idle Needed
~95% payed for IDLE

32.
Benefits of Serverless
$9.558,00
$5.150,40
$95,27
$95,27
$- $2.000,00 $4.000,00 $6.000,00 $8.000,00 $10.000,00 $12.000,00
t2.nano/each function
t2.medium/all functions
Cost over all annual imports
Lambda EC2
Cost savings about ~99%

33.
Benefits of Serverless
• Cost savings (Never pay for idle)
• 10 imports per month with 1,000 to 10,000 files each - as fast as possible
(scalability)
• Easy to extend and maintain
• Add, change or delete functions (microservice-approach)
• Configuration of each step (Failure-Handling, Resources)
• „No server is easier to manage than no server“
• Simple transformation of a monolith into microservices

34.
Looking forward
• Our Bottleneck:
RDS database and its limited scaling
• Costs associated with failover functions : 5%
• High costs for the operation of ES: 25%
(even ES is only needed for export queries)

35.
Thank you!
Nils Rhode // Haufe Group
nils.rhode@haufe-lexware.com
https://www.linkedin.com/in/nils-rhode/
Demo (Data Processing): https://dataprocessing.wildrydes.com/
Demo (Web App): https://github.com/aws-samples/aws-serverless-workshops/tree/master/WebApplication