This document discusses Haufe.Group's transition to a serverless architecture on AWS for one of its components, the EDB (court decision database). Key points:
- Haufe.Group is re-engineering its human resources system (HRS) from a monolith to microservices, starting with the EDB.
- The EDB architecture on AWS uses serverless workflows comprising Lambda functions and other serverless AWS services like S3.
- This has significantly reduced costs compared to using EC2 instances by eliminating idle capacity charges. It also improved scalability and made the system easier to maintain and extend.
- The next steps are to address bottlenecks from the RDS database and
2. Our True North Goal.
–
A family company for the
next generations.
3. 1880
employees
13
Locations in Germany
5
International branches
343 Mio.
Sales (2017)
All DAX 30
–
Companies rely on our expertise
150,000
–
Seminar participants at Haufe
Akademie every year
5,500,000
–
Users and licences
Our Solutions
Print
Software
Training
Consulting
Markets
Germany
Switzerland
USA
China
1934
founded as publishing house
Haufe is a family-operated business and we‘re very proud of beeing so and we would like to keep this up for the next generations
Founded 1934 as publishing house, Haufe derived to one of the leading companies in terms of transformation to digitization
About 1.800 employees spreaded over 20 locations all over the world – headquarter and most of location are within Germany
Haufe will generate sales of 370 € mio. euros in 2018
Haufe brand offers (amongst many other famous products like Lexware or the Haufe Akademie): specialist information, applications and services for the area of “tax and laws”.
For those apps, services and informations the ED of Haufe Group is responsible for this and that’s where I am hiring for.
The mentioned specialist informations are stored within the HRS system => HRS offers, beside the stored content, apps and services for interacting with the content
15 years old => just 6 month ago decided to reengineer and break down the monolith into microservices, starting with the first component „EDB“.
EDB is an own database within the whole HRS system, serving all content about court decision => 500.000….. => The overall functionality of EDB => Import, Improve, Export
AIM of Reengineering => future prood by state-of-the-art and to be able to integrate with technics like AI and ML in the future
Low maintenance => team about 5 developer, and just the first componenten out of a total of 7
Fast and cheap, because the import and export are running in irregular intervals (10 times import a month and exports every night)
Quick overview of how the EDB application looks like on AWS
Needed???? => would be the case „how to do it“ and „hot it‘s done by AWS – which is even nice and easy to understand“