RealDevSquad / RealDevSquad/website-backend

[RFC] migrate to DynamoDB

Open
#684 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation enhancement on-hold
Dominant language
JavaScript
Stars
74
Forks
276
Avg merge
1d 26m
Merged PRs (30d)
14

Description

Objectives

  • From a scalability perspective it much more scaleable
  • Has inbuilt cache support (something with Redis | ElastiCache)
  • Aggregation query is much better
  • Indexing
  • Right now Client side is deriving our database model
  • Database modeling is loosely packed
  • Limited Read/Write (Free Tier is much more benefiting)

Procedure

  • Creating Schema for the database
  • AWS migration tools (explore)
  • Middleware to write on both databases (zapier some ### tool)
  • Will use complete Typescript

V1 goals

  • API with higher traffic will be migrated first then otherwise i.e ()
  • Firestore and DynamoDB will co-exist
  • Schema Enforcing
  • Creating typescript objects according to the schema to share with frontend development
  • Documentation for migration and guidelines

End Goal

  • Completely build up DynamoDB and then slowly remove firestore
  • Database tightly packed with proper schema
  • A npm @types package for the database models (will be used on the frontend)
  • Fully migrated to typescript.
  • Database modeling will have a single source of truth

Supporting Docs

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points; begin with its Objectives, Procedure, and V1 goals, then review the linked AWS migration example. Done would require an agreed migration scope covering coexistence, schema enforcement, TypeScript models, migration documentation, and the eventual Firestore removal path.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, firebase, typescript
Domain
backend, cloud, database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.