Lyft switched their data store from Apache Druid to ClickHouse. We'll give brief overviews of Druid and ClickHouse and also talk about why they shifted.

Quastor's platform is  dedicated to providing insights and resources for software developers and technology enthusiasts, focusing on software architecture, design patterns, and system scalability. Through articles, case studies, and architecture reviews, Quastor offers insights into building robust and scalable software systems. Developers can learn about architectural principles, distributed systems, and microservices design to design and implement scalable and maintainable applications.

Quastor Daily

Lyft transitioned from using Apache Druid to ClickHouse for real-time data processing to handle their sub-second queries and extensive data needs. The shift addressed issues like Druid's steep maintenance learning curve and complex infrastructure. ClickHouse offered simplified management, reduced learning curves, data deduplication, lower costs, and specialized engines, despite facing some initial challenges such as query caching performance and Kafka ingestion issues.

How Lyft Processes Terabytes of Real Time Data

How to Implement Roles-based Access Control with AuthKit

The Developer’s Guide to Authorization and Implementing Role Based Access Controls