Remove Cache Remove Design Remove Lambda Remove Scalability
article thumbnail

Hashnode Creates Scalable Feed Architecture on AWS with Step Functions, EventBridge and Redis

InfoQ

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.

article thumbnail

AWS serverless services: Exploring your options

Dynatrace

Instead of worrying about infrastructure management functions, such as capacity provisioning and hardware maintenance, teams can focus on application design, deployment, and delivery. Scalability. Finally, there’s scalability. The first benefit is simplicity. Data Store. AWS offers four serverless offerings for storage.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Cloudburst: stateful functions-as-a-service

The Morning Paper

.’ Stateless is fine until you need state, at which point the coarse-grained solutions offered by current platforms limit the kinds of application designs that work well. On the Cloudburst design teams’ wish list: A running function’s ‘hot’ data should be kept physically nearby for low-latency access.

Lambda 98
article thumbnail

Embrace event-driven computing: Amazon expands DynamoDB with streams, cross-region replication, and database triggers

All Things Distributed

Streams provide you with the underlying infrastructure to create new applications, such as continuously updated free-text search indexes, caches, or other creative extensions requiring up-to-date table changes. DynamoDB Streams simplifies and improves this design pattern with a distributed systems approach.

Database 167
article thumbnail

Fast key-value stores: an idea whose time has come and gone

The Morning Paper

Why are developers using RInK systems as part of their design? Generally to cache data (including non-persistent data that never sees a backing store), to share non-persistent data across application services (e.g. We argue that RInK stores should not be used when implementing scalable data center services. Oh, you mean a cache?

Cache 79
article thumbnail

A one size fits all database doesn't fit anyone

All Things Distributed

As I have talked about before, one of the reasons why we built Amazon DynamoDB was that Amazon was pushing the limits of what was a leading commercial database at the time and we were unable to sustain the availability, scalability, and performance needs that our growing Amazon.com business demanded. Purpose-built databases.

Database 167
article thumbnail

Choosing a cloud DBMS: architectures and tradeoffs

The Morning Paper

Which I’m quite happy to see as my most recent data pipeline is based around Lambda, S3, and Athena, and it’s been working great for my use case. The design space. Query performance is measured from both warm and cold caches. Scalability. Query restrictions.