Tag: Technical Use Cases

This post is part 1 of a two-part series. In this post, I focus on data modeling with DynamoDB. I describe an example use case to demonstrate alternative ways of modeling the same data, and the pros and cons of each approach. Proper data modeling is an essential prerequisite to beginning the development of a back end service.

Branch’s Node.js application servers were at 80% CPU, and our PostgresSQL RDS looked like it didn’t have much more room to grow. Meanwhile, traffic was doubling every couple of weeks. They had to figure out a pathway to scale quickly. Here’s what they did.

Post by Sunil Mallya, Solutions Architect, AWS Time is the most critical component in the startup equation. Startups should maximize their time with customers and focus on building a better product, not spending their time managing infrastructure and servers. Amazon continues to build services that abstract complex components and focus on making it easy to […]

At Clarify.io, we put pipelines on our “really going to do” list. By adopting a pipeline-based approach, we gained immediate returns that we could measure in hard numbers like less downtime, faster release schedules, and reliable fixes. Pipelines made our software more stable, easier to maintain, and safer to change. Here are the benefits and how to get started.

Scaling an on-premise infrastructure is hard. You need to plan for peak capacity, wait for equipment to arrive, configure the hardware and…

By Todd Varland, Jeremy Wallace, and Henrik Johansson
Solutions Architects, AWS

When you’re building new web applications and simultaneously trying to grow your customer base, there are a lot of competing concerns you…

Simplicity is prerequisite for reliability. — Edsger W. Dijkstra

Titan is a distributed graph database that now supports DynamoDB.

In part one, AWS Lambda and DynamoDB Streams were in preview mode. Since their recent launch, some portions of the API have changed. This post reflects the latest updated coding conventions of each.