DynamoDB Schema Reviews
Async delivery in 3–7 business days. No calls required.
DynamoDB schema mistakes are expensive. A wrong key structure means a migration across millions of items. A missing GSI means a table scan in production. A hot partition means throttling at the worst possible time.
A second pair of eyes before you commit to production saves weeks of migration work later.
How it works
- You fill out the intake form. Your entities, access patterns, current tech stack, and any constraints.
- I design or review your schema. PK/SK structure, GSI strategy, ElectroDB entity definitions, and a written analysis explaining every design decision.
- You get the deliverable within 5 business days. Everything you need to start building.
You get a document you can hand to your team and build from.
Three tiers
Starter
$149Schema design with PK/SK structure, access pattern mapping, and GSI recommendations. ~4 page deliverable.
Scope: Up to 5 access patterns, 1–2 entity types.
- ✓ PK/SK structure with access pattern mapping
- ✓ GSI recommendations with rationale
- ✓ One-paragraph rationale per major design decision
- ✓ One round of async follow-up questions
Turnaround: 3–5 business days.
Best for: Validating an early design before you write code.
Standard
$299Everything in Starter, plus schema diagram, ElectroDB index code, sample data, and trade-off summary. ~8 page deliverable.
Scope: Up to 15 access patterns, up to 5 entity types.
- ✓ Everything in Starter
- ✓ Schema diagram with entity relationships
- ✓ ElectroDB index definitions — PK/SK/GSI templates per entity (TypeScript, copy-paste ready)
- ✓ Sample data table showing actual DynamoDB items
- ✓ Trade-off summary covering what the schema doesn't support
Turnaround: 5 business days.
Best for: Greenfield builds that need production-ready entity structure.
Premium
$499The complete review. Everything in Standard, plus full ElectroDB entity code, cost analysis, complete trade-off analysis, and recommended next steps. ~14 page deliverable.
Scope: No limit on access patterns or entity types.
- ✓ Everything in Standard
- ✓ Full ElectroDB entity code — complete attribute definitions, defaults, enums, and watch logic (production-ready TypeScript)
- ✓ Cost analysis: RCU/WCU per access pattern, monthly projection
- ✓ Complete trade-off analysis with recommended next steps
- ✓ Migration plan if you're restructuring an existing table
- ✓ Loom walkthrough explaining every design decision (~10 min)
- ✓ One full round of async revisions after your team reviews
Turnaround: 7 business days.
Best for: Production schemas and high-stakes designs.
What I need from you
The intake form asks for:
- Project description - what does the app do, who uses it
- Entity list - each entity with its key attributes (e.g., User: userId, email, name, role)
- Access patterns - numbered list of every query your app needs (e.g., "Get all orders for a customer, newest first")
- Current tech stack - CDK, SST, Terraform, SAM, or other
- Preferred ORM - ElectroDB, DynamoDB-Toolbox, Dynamoose, or raw SDK
- Constraints - anything unusual (regulatory requirements, extreme scale, existing table structure)
The more specific your access patterns, the better the schema. "Get user data" is vague. "Get user by email for authentication, returning userId, name, and role" is actionable.
Why me
I've built production DynamoDB apps with single-table design for rasika.life (a cultural events platform with 6+ GSIs per entity), property management tools, and e-commerce backends. I maintain the singletable.dev pattern library - 10+ schema patterns with full ElectroDB implementations.
I'm not a DynamoDB evangelist. I wrote "When NOT to Use Single-Table Design" because honest tradeoff analysis matters more than advocacy. If your use case is better served by Postgres, I'll tell you that.
Sample deliverable
Here's a complete Premium-tier review for a fictional HR SaaS: 12 access patterns, 5 entity types, one overloaded GSI, full ElectroDB entity code, cost analysis, and a trade-off section covering what the schema explicitly doesn't support. ~14 pages.
Acme HR SaaS — Premium Tier Sample
12 access patterns · 5 entities · 1 overloaded GSI · full ElectroDB code · cost analysis · trade-off analysis · recommended next steps
The sample is the same document you'd receive. The only difference is it covers a fictional company, not yours.
First 10 reviews: 30% off
I'm offering the first 10 reviews at 30% off to build the portfolio. Use code EARLY30 at checkout - valid for the first 10 signups.
| Tier | Regular | Early bird |
|---|---|---|
| Starter | $149 | $104 |
| Standard | $299 | $209 |
| Premium | $499 | $349 |
FAQ
What counts as "1 access pattern"?
One access pattern = one distinct query your code makes against DynamoDB. "Get user by userId" is one. "Get all orders for a customer, sorted by date" is another. "Get all products in a category by price range" is a third. If you write a separate query() call for it, it's a separate pattern. Easiest check: count your distinct query() calls.
Do you sign NDAs?
Yes. Mutual NDA available on request before you share anything sensitive. Email me at singletabledev@gmail.com and I'll send one over before the intake form.
What if I need a revision?
Starter and Standard include one round of async follow-up questions after delivery. Premium includes one full revision round. You review the deliverable with your team, send consolidated feedback, and I update the schema. If your requirements change significantly mid-review (new entities, major scope shift), we'll discuss a scope adjustment before proceeding.
Can I upgrade tiers after submitting the intake form?
Yes. If your schema turns out to be more complex than expected, you can upgrade by paying the difference. I'll flag this before starting work if I think your scope doesn't match the tier you selected.
What's your refund policy?
Full refund if you cancel before I start work. Prorated refund based on work completed if you cancel after I've begun. No refunds after delivery. But if the deliverable doesn't cover what was agreed in the intake form, I'll fix it.
Do you do hourly consulting?
No. Fixed-tier only, by design. Hourly billing creates incentives to take longer; fixed scope creates incentives to be precise. You know the cost upfront, and I stay focused on the deliverable rather than the clock.
I'm in a different timezone — does that affect turnaround?
No. Turnaround is measured in business days from the day I accept your intake. Since delivery is async, timezone doesn't matter. The deliverable shows up in your inbox.
Not sure which tier? Start with the intake form. I'll recommend the right tier based on your schema complexity.