Harnessing Amazon’s DynamoDB with Spring
summary
Migrating a legacy OSGi stack to Spring with AWS services yields a single-table DynamoDB design keyed by partition organization and a sort key that prefixes entries with parent IDs, plus a global index called GSI1. Uses AWS SDK v2 but falls back to the low-level DynamoDB client for complex filter expressions (filter strings are brittle), resulting in a three-request flow (teams, tasks, resources) to assemble user-visible data. Deploys with Terraform, CircleCI and Testcontainers, runs on Java 11, and reuses code in Lambda via a minimal ApplicationContext.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:19Who is Iuliana
- 1:56Disclaimer
- 2:59My Plan
- 3:33Architecture
- 5:37Migration
- 10:26Challenges
- 12:11Whats the Catch
- 15:59Global Secondary Indices
- 17:34Connecting to DynamoDB
- 18:27Repository
- 20:43Simple Scenario
- 21:28Complex Scenario
- 23:10Sort Key
- 24:11Service Method
- 24:47Query Expressions
- 26:04Query Request
- 27:02Bonus
- 29:35Conclusion
related talks
33mDynamoDB Essentials and Integration for Java Developers
51mImmutable data stores and CORS for safety, flexibility and profit
47mEvent-driven Serverless Architecture with DynamoDB
30mBuild for Scale, Performance With Feature-packed Amazon DynamoDB
33mBuild for scale with Amazon DynamoDB developer features
01h 23mBuilding Highly-Scalable Spring Applications with In-Memory, Distributed Data Grids
21mSave, Grow and Innovate using AWS Databases
41mDynamoDB, Neptune and OpenSearch: A Unified Approach to Collaborative Editing and Search #JSConfAM25