ERP System and database Administrator
Budget: $250 – $750 USD
I’m planning a new database-centric platform and I need help at the very first stage: solid system design. The core of the project is a full-featured Database Management System, but I want to concentrate our initial effort on one critical area—robust data backup and recovery.
Here’s what I need from you:
• Translate my high-level requirements into an end-to-end database architecture (schema design, storage engine choice, indexing strategy and capacity planning).
• Map out a fault-tolerant backup workflow that covers automated dumps, point-in-time recovery, off-site/ cloud replication and clear RTO/RPO targets.
• Document the design thoroughly so an implementation team can pick it up without guesswork: diagrams, component specs, backup schedules, recovery playbooks and security considerations.
Acceptance criteria
• A design document (PDF or Markdown) including ER diagrams, technology stack rationale and a step-by-step recovery procedure.
• All decisions justified with pros/cons so stakeholders can sign off confidently.
• The solution must be vendor-agnostic enough to work with platforms such as PostgreSQL, MySQL or MariaDB, yet detailed enough to implement on one of them immediately.
If you’ve architected database systems with rigorous backup and recovery guarantees before, I’d love to see how you’d tackle this.
Here’s what I need from you:
• Translate my high-level requirements into an end-to-end database architecture (schema design, storage engine choice, indexing strategy and capacity planning).
• Map out a fault-tolerant backup workflow that covers automated dumps, point-in-time recovery, off-site/ cloud replication and clear RTO/RPO targets.
• Document the design thoroughly so an implementation team can pick it up without guesswork: diagrams, component specs, backup schedules, recovery playbooks and security considerations.
Acceptance criteria
• A design document (PDF or Markdown) including ER diagrams, technology stack rationale and a step-by-step recovery procedure.
• All decisions justified with pros/cons so stakeholders can sign off confidently.
• The solution must be vendor-agnostic enough to work with platforms such as PostgreSQL, MySQL or MariaDB, yet detailed enough to implement on one of them immediately.
If you’ve architected database systems with rigorous backup and recovery guarantees before, I’d love to see how you’d tackle this.
Related categories:
PHP
Linux
Project Management
SQL
Software Testing
Website Testing
Chrome OS
Microsoft
Website Management
Web Hosting