Syncora brings collaborative team workflows into one application, with a backend organized around clear DTO mapping and layered responsibilities.
The problem
Team collaboration needs timely updates, authenticated access and predictable data boundaries. The documented implementation uses Ably Realtime for realtime communication, not a direct WebSocket claim.
Technical deep dive
How the system holds together.
Realtime Communication
Ably is the documented realtime communication layer. This keeps the case study accurate without describing the project as a direct WebSocket implementation.
Authentication and Layers
OAuth2 and DTO mapping support a boundary between transport models and application data. The backend is presented as layered rather than as a collection of route handlers.
Database
PostgreSQL is part of the documented stack. Exact entities and endpoint names are left to the implementation source rather than being invented in this portfolio.
Diagrams
System surfaces.
ARCHITECTURESyncora Architecture
AUTHENTICATIONAuthenticated Collaboration
DEPLOYMENTApplication Shape
Engineering decisions
Why I made these decisions.
Why Ably?
The documented realtime layer is Ably, which keeps event delivery separate from the core Spring Boot API.
Why DTO mapping?
Explicit DTO boundaries keep transport contracts separate from persistence models.
Why layered architecture?
Separating controllers, services and data access makes collaboration features easier to reason about and change.
Testing
The portfolio documents API-oriented development, but does not claim unverified test coverage or test cases.
Deployment & DevOps
AWS appears in the documented stack. Specific services are intentionally not named without the backend deployment source.