Database Design Advice
- or -
Post a project like this$$
- Posted:
- Proposals: 5
- Remote
- #1754388
- Expired
Description
Experience Level: Intermediate
Estimated project duration: less than 1 week
General information for the website: Heavy usage database system design
Database management system (DBMS): MySQL
Description of requirements/features: We are looking for an established database systems engineer to provide guidance on the design of a database system for a new project.
At present this is exploratory, so the deliverable is a fully-documented database schema, detailing tables, fields/field types, indexes etc... for the proposed project, along with a background on the benefits to the proposed design. Also included in the deliverables should be examples of the most efficient query strings for certain operations - details of which will be provided to the winning bid.
The system should work around normalised data and deliver the fastest possible response to queries, which may be complexed and involved at times. Speed of query response is critical. This project will be public facing and based around the UK transport industry.
The system will be operated 24/7 likely on a cloud database system (such as Amazon Aurora), with the server processing for the website front end being handled through Amazon EC2 instances in a load balanced scenario. Significant amounts of data (upwards of 3-4GB) will be fed into the system each day, through a four or possibly five different sources, there will be a master update file added in during the early hours of each morning which may vary each day from a few KB to several GB. This will upwards of 40% new records, with the remainder being deletions or updates. All data will be fed into the system from a queue (potentially using AWS SQS) to ensure that no data is lost. The database system on the whole will be read/query heavy.
We envisage that there is likely to be between four and six core data tables, with some queries needing to pull information from all of them. The results of certain queries may be cached in JSON format, in a separate database table, while others must be generated each time to ensure accurate data is returned.
Query rate for the database is expected to be in the 1,000s each day, potentially increasing over time.
Further details and examples of the kind of data and queries can be provided to serious parties. While further work may follow this is a one-off database design project. There is currently no programming of physical work on a database server required.
Because of the nature of the work, and communication necessary - we are only looking for bidders with perfect English, who are based within Western Europe, the United Kingdom, United States or Canada. Working across time differences does not usually cause any issues with ourselves.
Extra notes:
Database management system (DBMS): MySQL
Description of requirements/features: We are looking for an established database systems engineer to provide guidance on the design of a database system for a new project.
At present this is exploratory, so the deliverable is a fully-documented database schema, detailing tables, fields/field types, indexes etc... for the proposed project, along with a background on the benefits to the proposed design. Also included in the deliverables should be examples of the most efficient query strings for certain operations - details of which will be provided to the winning bid.
The system should work around normalised data and deliver the fastest possible response to queries, which may be complexed and involved at times. Speed of query response is critical. This project will be public facing and based around the UK transport industry.
The system will be operated 24/7 likely on a cloud database system (such as Amazon Aurora), with the server processing for the website front end being handled through Amazon EC2 instances in a load balanced scenario. Significant amounts of data (upwards of 3-4GB) will be fed into the system each day, through a four or possibly five different sources, there will be a master update file added in during the early hours of each morning which may vary each day from a few KB to several GB. This will upwards of 40% new records, with the remainder being deletions or updates. All data will be fed into the system from a queue (potentially using AWS SQS) to ensure that no data is lost. The database system on the whole will be read/query heavy.
We envisage that there is likely to be between four and six core data tables, with some queries needing to pull information from all of them. The results of certain queries may be cached in JSON format, in a separate database table, while others must be generated each time to ensure accurate data is returned.
Query rate for the database is expected to be in the 1,000s each day, potentially increasing over time.
Further details and examples of the kind of data and queries can be provided to serious parties. While further work may follow this is a one-off database design project. There is currently no programming of physical work on a database server required.
Because of the nature of the work, and communication necessary - we are only looking for bidders with perfect English, who are based within Western Europe, the United Kingdom, United States or Canada. Working across time differences does not usually cause any issues with ourselves.
Extra notes:
RH M.
100% (11)Projects Completed
11
Freelancers worked with
9
Projects awarded
43%
Last project
2 May 2020
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies