# Reducing microservice startup time with highly available Redis data storage

DevFeed: [Reducing microservice startup time with highly available Redis data storage](<https://devfeed.tech/articles/how-we-got-on-top-of-our-data-28021.md>)

Original publisher: [Read original article](<https://tech.trivago.com/post/2022-05-04-how-we-got-on-top-of-our-data/>)

Author: Kevin Beineke

Published: 2022-05-04T00:00:00Z

Content type: article

Language: en

Sources: [Trivago](<https://devfeed.tech/sources/trivago.md>)

Topics: [Redis](<https://devfeed.tech/topics/redis.md>), [Microservice](<https://devfeed.tech/topics/microservice.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Java](<https://devfeed.tech/topics/java.md>)

Tags: [availability](<https://devfeed.tech/tags/availability.md>), [backend](<https://devfeed.tech/tags/backend.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [redis](<https://devfeed.tech/tags/redis.md>), [scalability](<https://devfeed.tech/tags/scalability.md>)

## AI overview

The trivago backend consumes accommodation data in a Java-based microservice. Its previous approach loaded gigabytes of data into memory at startup and updated it from a stream, causing startup times of more than five minutes. The article describes addressing these operational and scaling problems by controlling data updates and using a highly available Redis setup.

## Source excerpt

Scalability and availability are key aspects of cloud native computing. If your microservice takes five minutes to start up, it becomes very difficult to meet the expectations because adjustment...