InfoQ Homepage Key-Value Store Content on InfoQ
-
Valkey 8.0 Now Generally Available with Improved Memory Efficiency
The Linux Foundation has announced the general availability of Valkey 8.0, the open source in-memory storage solution developed as a successor to Redis. By introducing a dictionary per slot and embedding keys directly into dictionary entries, developers can achieve up to 20% more capacity, allowing for the storage of additional keys per node.
-
Netflix’s Pushy: Evolution of Scalable WebSocket Platform That Handles 100Ms Concurrent Connections
Netflix shared details on the evolution of Pushy, a WebSocket messaging platform that supports push notifications and inter-device communication across many different devices for the company’s products. Netflix’s engineers implemented many improvements across the Pushy ecosystem to ensure the platform's scalability and reliability and support new capabilities.
-
QCon London: How Duolingo Sent 4 Million Push Notifications in 6 Seconds During the Super Bowl Break
As part of the Super Bowl marketing campaign, Duolingo sent out 4 million mobile push notifications when the company’s five-second ad aired during the commercial break. At QCon London, Doulingo’s engineers presented the asynchronous AWS architecture responsible for broadcasting messages to millions of users across seven US cities.
-
Microsoft Announces Garnet: a New Open-Source Cache-Store and Redis Alternative
Microsoft Research has recently announced Garnet, an open-source cache-store designed to accelerate applications and services. Using the RESP wire protocol, Garnet is a faster alternative to cache-stores and is compatible with existing Redis clients.
-
Redis Switches to SSPLv1: Restrictive License Sparks Fork by Former Maintainers
Redis has recently announced a change in their license by transitioning from the open-source BSD to the more restrictive Server Side Public License (SSPLv1). The move has promptly led to a fork initiated by former maintainers and reignited discussions surrounding the sustainability of open-source initiatives.
-
Hashnode Creates Scalable Feed Architecture on AWS with Step Functions, EventBridge and Redis
Hashnode created a scalable event-driven architecture (EDA) for composing feed data for thousands of users. The company used serverless services on AWS, including Lambda, Step Functions, EventBridge, and Redis Cache. The solution leverages Step Functions' distributed maps feature that enables high-concurrency processing.
-
The Guardian Creates a Newsroom Collaboration Tool Using Serverless, React and GraphQL
The Guardian created Pinboard, a discussion and asset-sharing tool integrated into a variety of content management platforms used by the company. The solution uses a range of technologies, including Typescript for coding the business logic, different serverless services for code execution, API endpoints, and GraphQL server, as well as AWS RDS (PostgreSQL) for storage.
-
Uber's CacheFront: Powering 40M Reads per Second with Significantly Reduced Latency
Uber developed an innovative caching solution, CacheFront, for its in-house distributed database, Docstore. CacheFront enables over 40M reads per second from online storage and achieves substantial performance improvements, including a 75% reduction in P75 latency and over 67% reduction in P99.9 latency, demonstrating its effectiveness in enhancing system efficiency and scalability.
-
Async Ops and Scalable Keyspaces Make Threads Go Viral
Meta's Engineering team has published a post explaining how they built the infrastructure for Threads, their new online social media and networking service. The decision to launch was abrupt, with the infrastructure teams having just two days' notice. However, the teams were confident in Meta's infrastructure's maturity and past performance to effectively support the app's rapid growth.
-
lastminute.com Improves Search Scalability Using Microservices with RabbitMQ and Redis
The team at lastminute.com rearchitected the search result aggregation process by breaking up the single service into multiple ones and introducing asynchronous integration. Developers used RabbitMQ for messaging and Redis for storing results from data suppliers. The revised architecture improved scalability and deployability and reduced resource utilization.
-
Zendesk Moves from DynamoDB to MySQL and S3 to Save over 80% in Costs
Zendesk reduced its data storage costs by over 80% by migrating from DynamoDB to a tiered storage solution using MySQL and S3. The company considered different storage technologies and decided to combine the relational database and the object store to strike a balance between querybility and scalability while keeping the costs down.
-
Amazon ElastiCache Serverless: a New Option for Scaling Cache Capacity Instantly
AWS recently announced the general availability of Amazon ElastiCache Serverless, a new serverless option allowing users to quickly create a cache and instant scale capacity based on application traffic patterns. In addition, the serverless option is compatible with open-source caching solutions Redis and Memcached.
-
AWS Introduces Amazon CloudFront KeyValueStore: a Low Latency Datastore for CloudFront Functions
AWS recently announced Amazon CloudFront KeyValueStore, a secure global low-latency key-value datastore that allows read access from within CloudFront Functions, enabling advanced customizable logic at the CloudFront edge locations.
-
.NET Aspire: Cloud-Native App Development with Microsoft's Latest Project
Microsoft released .NET 8 last week; one of the most notable news within the launch was .NET Aspire, the cloud-native development stack for building resilient, observable, and configurable cloud-native applications with the dotnet. .NET Aspire includes a curated set of components enhanced for cloud-native by including service discovery, telemetry, resilience, and health checks by default.
-
How DoorDash Rearchitected its Cache to Improve Scalability and Performance
DoorDash rearchitected the heterogeneous caching system they were using across all of their microservices and created a common, multi-layered cache providing a generic mechanism and solving a number of issues coming from the adoption of a fragmented cache.