Real-Time Database Integration Updates
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted1 hour ago
I need my application wired to a back-end database so that every new or changed record is reflected instantly on the front-end dashboards. Real-time updates are the only reporting style I will accept; batch or scheduled exports will not meet the requirement.
The core work involves:
• Connecting the chosen data store to my existing codebase (language-agnostic at this stage; you may recommend SQL, NoSQL, or an in-memory solution after reviewing my load profile).
• Building the live data pipeline—triggers, change streams, or pub/sub—as appropriate.
• Rendering the real-time views in a lightweight reporting layer so end-users see changes within seconds.
• Supplying clean, well-commented code and a short deployment guide that lets me reproduce the setup on staging and production.
Completion is verified when I can:
1. Insert or update a record through an API or admin panel and watch the corresponding dashboard component refresh without a manual reload.
2. View latency logs showing sub-second propagation under a modest test load.
3. Follow your documentation to recreate the environment from scratch.
If WebSockets, Kafka, Firebase, MongoDB change streams, or Postgres LISTEN/NOTIFY feel like the right fit, mention why; I'm open.
The core work involves:
• Connecting the chosen data store to my existing codebase (language-agnostic at this stage; you may recommend SQL, NoSQL, or an in-memory solution after reviewing my load profile).
• Building the live data pipeline—triggers, change streams, or pub/sub—as appropriate.
• Rendering the real-time views in a lightweight reporting layer so end-users see changes within seconds.
• Supplying clean, well-commented code and a short deployment guide that lets me reproduce the setup on staging and production.
Completion is verified when I can:
1. Insert or update a record through an API or admin panel and watch the corresponding dashboard component refresh without a manual reload.
2. View latency logs showing sub-second propagation under a modest test load.
3. Follow your documentation to recreate the environment from scratch.
If WebSockets, Kafka, Firebase, MongoDB change streams, or Postgres LISTEN/NOTIFY feel like the right fit, mention why; I'm open.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.