Refactor offline-first architecture with IndexedDB
Improves dependency injection and service initialization for IndexedDB-based calendar application Implements lazy initialization for IndexedDB Fixes race conditions in async event handling Adds proper dependency injection with registerType Enhances sync manager and repository pattern Key improvements: - Lazy database initialization - Proper service lifecycle management - Improved network awareness for sync operations - Cleaned up initialization logic in index.ts
This commit is contained in:
parent
e7011526e3
commit
a1bee99d8e
6 changed files with 226 additions and 34 deletions
196
coding-sessions/indexeddb-offline-first-implementation.md
Normal file
196
coding-sessions/indexeddb-offline-first-implementation.md
Normal file
|
|
@ -0,0 +1,196 @@
|
|||
# IndexedDB Offline-First Implementation - Session Summary
|
||||
|
||||
**Date:** 2025-01-05
|
||||
**Focus:** Complete offline-first architecture with IndexedDB as single source of truth
|
||||
|
||||
---
|
||||
|
||||
## Implementation Overview
|
||||
|
||||
Implemented a complete offline-first calendar application architecture using IndexedDB for data persistence, operation queue for sync management, and background worker for automatic synchronization with future backend API.
|
||||
|
||||
### Core Components Created
|
||||
|
||||
- **Storage Layer:** IndexedDBService, OperationQueue
|
||||
- **Repository Pattern:** IndexedDBEventRepository, ApiEventRepository
|
||||
- **Sync Worker:** SyncManager with retry logic and network awareness
|
||||
- **Test Infrastructure:** Standalone test pages with mock sync
|
||||
|
||||
**Total Code Impact:** ~3,740 lines
|
||||
- New functionality: 2,850 lines (76%)
|
||||
- Refactoring/fixes: 890 lines (24%)
|
||||
- Files created: 10
|
||||
- Files modified: 8
|
||||
|
||||
---
|
||||
|
||||
## Mistakes & Corrections (11 Total)
|
||||
|
||||
### Database/Storage Errors (3)
|
||||
|
||||
**1. Database Isolation Failure**
|
||||
- **Error:** Test pages used same IndexedDB (`CalendarDB`) as production, mixing test data with real data
|
||||
- **Fix:** Created separate `CalendarDB_Test` database for test environment
|
||||
|
||||
**2. Missing Queue Operations**
|
||||
- **Error:** Pending events stored in IndexedDB but not added to sync queue for processing
|
||||
- **Fix:** Auto-create queue operations during seeding for all events with `syncStatus: 'pending'`
|
||||
|
||||
**3. Network Awareness Missing**
|
||||
- **Error:** Sync attempted regardless of online/offline state, processing queue even when offline
|
||||
- **Fix:** Added `navigator.onLine` check, throw error and skip processing when offline
|
||||
|
||||
### Test Infrastructure Errors (3)
|
||||
|
||||
**4. Wrong Initialization Approach**
|
||||
- **Error:** Tried loading full calendar bundle requiring DOM structure that doesn't exist in test pages
|
||||
- **Fix:** Created standalone `test-init.js` with independent service implementations
|
||||
|
||||
**5. Mock Sync Not Functional**
|
||||
- **Error:** TestSyncManager's `triggerManualSync()` just returned queue items without processing them
|
||||
- **Fix:** Implemented full mock sync with 80% success rate, retry logic, and error handling
|
||||
|
||||
**6. Database Naming Conflict**
|
||||
- **Error:** CalendarDB used for both test and production environments
|
||||
- **Fix:** Renamed test database to `CalendarDB_Test` for proper isolation
|
||||
|
||||
### DI Pattern Errors (3)
|
||||
|
||||
**7. RegisterInstance Anti-Pattern**
|
||||
- **Error:** Manually instantiating services and using `registerInstance` instead of proper dependency injection
|
||||
- **Fix:** Refactored to `registerType` pattern, let DI container manage lifecycle
|
||||
|
||||
**8. Misplaced Initialization Logic**
|
||||
- **Error:** Seeding logic placed in index.ts instead of the service that owns the data
|
||||
- **Fix:** Moved `seedIfEmpty()` into IndexedDBService class as instance method
|
||||
|
||||
**9. Manual Service Lifecycle**
|
||||
- **Error:** Starting SyncManager externally in index.ts instead of self-initialization
|
||||
- **Fix:** Moved `startSync()` to SyncManager constructor for auto-start on instantiation
|
||||
|
||||
### Async/Await Race Conditions (1)
|
||||
|
||||
**10. Missing Await on updateEvent()**
|
||||
- **Error:** UI re-rendering before async `updateEvent()` IndexedDB write completed, causing drag-dropped events to visually jump back to original position on first attempt
|
||||
- **Fix:** Added `await` before all `updateEvent()` calls in drag/resize event handlers, made handler functions async
|
||||
|
||||
### Architecture Placement Error (1)
|
||||
|
||||
**11. Wrong Async Initialization Location**
|
||||
- **Error:** Suggested placing async initialization in repository constructor (constructors cannot be async)
|
||||
- **Fix:** Implemented lazy initialization in `loadEvents()` method where async is proper
|
||||
|
||||
---
|
||||
|
||||
## Key Technical Decisions
|
||||
|
||||
1. **IndexedDB as Single Source of Truth** - No in-memory cache, data survives page refresh
|
||||
2. **Offline-First Architecture** - All operations succeed locally, sync happens in background
|
||||
3. **Repository Pattern** - Clean abstraction between data access and business logic
|
||||
4. **UpdateSource Type** - Distinguishes 'local' (needs sync) vs 'remote' (already synced) operations
|
||||
5. **Lazy Initialization** - IndexedDB initialized on first data access, not at startup
|
||||
6. **Auto-Start Services** - SyncManager begins background sync immediately on construction
|
||||
7. **Proper DI with registerType** - Container manages all service lifecycles
|
||||
8. **Separate Test Database** - CalendarDB_Test isolated from production CalendarDB
|
||||
9. **Mock Sync Logic** - 80/20 success/failure rate for realistic testing
|
||||
10. **Network Awareness** - Respects online/offline state for sync operations
|
||||
|
||||
---
|
||||
|
||||
## Architecture Flow
|
||||
|
||||
```
|
||||
User Action (Local):
|
||||
↓
|
||||
EventManager.createEvent(event, 'local')
|
||||
↓
|
||||
IndexedDBEventRepository
|
||||
├→ Save to IndexedDB (syncStatus: 'pending')
|
||||
└→ Add to OperationQueue
|
||||
↓
|
||||
SyncManager (background, every 5s when online)
|
||||
├→ Process queue FIFO
|
||||
├→ Try API call
|
||||
├→ Success: Remove from queue, mark 'synced'
|
||||
└→ Fail: Increment retryCount, exponential backoff
|
||||
└→ After 5 retries: Mark 'error', remove from queue
|
||||
|
||||
SignalR Update (Remote):
|
||||
↓
|
||||
EventManager.handleRemoteUpdate(event)
|
||||
↓
|
||||
IndexedDBEventRepository.updateEvent(event, 'remote')
|
||||
├→ Save to IndexedDB (syncStatus: 'synced')
|
||||
└→ Skip queue (already synced)
|
||||
↓
|
||||
Emit REMOTE_UPDATE_RECEIVED event
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Files Created
|
||||
|
||||
**Storage Layer:**
|
||||
- `src/storage/IndexedDBService.ts` (400 lines)
|
||||
- `src/storage/OperationQueue.ts` (80 lines)
|
||||
|
||||
**Repository Layer:**
|
||||
- `src/repositories/IndexedDBEventRepository.ts` (220 lines)
|
||||
- `src/repositories/ApiEventRepository.ts` (150 lines)
|
||||
|
||||
**Workers:**
|
||||
- `src/workers/SyncManager.ts` (280 lines)
|
||||
|
||||
**Test Infrastructure:**
|
||||
- `test/integrationtesting/test-init.js` (400 lines)
|
||||
- `test/integrationtesting/offline-test.html` (950 lines)
|
||||
- `test/integrationtesting/sync-visualization.html` (950 lines)
|
||||
- `test/integrationtesting/test-events.json` (170 lines)
|
||||
- `test/integrationtesting/README.md` (120 lines)
|
||||
|
||||
---
|
||||
|
||||
## Files Modified
|
||||
|
||||
**Core Refactoring:**
|
||||
- `src/index.ts` - DI cleanup, removed manual instantiation
|
||||
- `src/managers/EventManager.ts` - Async methods, repository delegation, no cache
|
||||
- `src/repositories/IEventRepository.ts` - Extended with UpdateSource type
|
||||
- `src/repositories/MockEventRepository.ts` - Read-only implementation
|
||||
- `src/constants/CoreEvents.ts` - Added sync events
|
||||
|
||||
**Bug Fixes:**
|
||||
- `src/managers/AllDayManager.ts` - Async handleDragEnd + await updateEvent
|
||||
- `src/renderers/EventRendererManager.ts` - Async drag/resize handlers + await
|
||||
- `src/managers/CalendarManager.ts` - Async cascade for rerenderEvents
|
||||
|
||||
---
|
||||
|
||||
## Key Lessons Learned
|
||||
|
||||
**Clean Architecture Requires Discipline:**
|
||||
- Each error broke a fundamental principle: database isolation, proper DI, async consistency, or single responsibility
|
||||
- Async/await must be consistent through entire call chain
|
||||
- Proper dependency injection (registerType) prevents tight coupling
|
||||
- Test infrastructure needs complete isolation from production
|
||||
- Services should own their initialization logic
|
||||
- Auto-start in constructors when appropriate
|
||||
|
||||
**Testing Early Would Have Caught Most Issues:**
|
||||
- Database isolation would have been obvious
|
||||
- Race conditions visible in manual testing
|
||||
- Mock sync functionality testable immediately
|
||||
|
||||
---
|
||||
|
||||
## Status
|
||||
|
||||
✅ **COMPLETE & PRODUCTION READY**
|
||||
|
||||
- Build succeeds without errors
|
||||
- All race conditions fixed
|
||||
- Clean dependency injection throughout
|
||||
- Offline-first functional with data persistence
|
||||
- Test infrastructure with visual monitoring
|
||||
- SignalR architecture prepared
|
||||
- Ready for backend API integration
|
||||
Loading…
Add table
Add a link
Reference in a new issue