Expert Needed for PostgreSQL Cloud Database API
Budget: $25 – $50 USD
(Azure) (Cloud Storage) (API) (SQL) (NoSQL) (RESTful)
We produce radio frequency identification (“RFID”) readers and use several proprietary applications during production, fulfillment, software licensing and support of our hardware products. These applications are written in C++ and Java and run on Windows. Our contract manufacturers and fulfillment centers use these proprietary applications which produce a variety of files and data stored locally during production of each device. Information regarding post-production sales of software add-on features is also stored in the database. Each operations location generates local SQLite databases and other data files which are individually copied to our home office and merged to contain data from all locations.
We want to move to a cloud database model, using Azure, and need an Interface Layer between these custom C++ and Java applications and the cloud storage. The cloud storage is likely PostgreSQL but is negotiable in the design process. The Interface Layer will have a well-defined API to query, access, read and write to the cloud database(s). The API will be available from C++, Java, and Python applications. The architecture must be able to locally cache data/commits in the event access to Azure is temporarily unavailable, as to not interfere with production. The data will automatically be pushed to Azure when connectivity is restored. The type of data includes traditional SQL-type record storage with several related text (~1Mb ea.) and binary (~250Mb ea.) files per device manufactured. The current total data store (SQLite databases and related files) is approximately 600Gb. Transaction frequency is relatively low; on the order of minutes during device manufacturing and fulfillment, with manufacturing periods lasting several weeks. Access concurrency is also relatively low. The API, architecture and storage model are negotiable and part of the design process.
Summary of tasks
1. Review and discuss the current requirements documentation.
2. Present a design approach for discussion and approval.
3. Implement the approved design.
4. Provide documentation for the API.
5. Migrate existing data SQLite databases to the unified cloud-based storage.
Successful applicants should ideally have:
* Proven experience in Cloud Database API development.
* Strong knowledge of PostgreSQL.
* A deep understanding of various data types and how to efficiently store and manipulate them in a database.
Only those with relevant skills and experience, apply. Please showcase your past work related to Cloud-based database projects when bidding.
We produce radio frequency identification (“RFID”) readers and use several proprietary applications during production, fulfillment, software licensing and support of our hardware products. These applications are written in C++ and Java and run on Windows. Our contract manufacturers and fulfillment centers use these proprietary applications which produce a variety of files and data stored locally during production of each device. Information regarding post-production sales of software add-on features is also stored in the database. Each operations location generates local SQLite databases and other data files which are individually copied to our home office and merged to contain data from all locations.
We want to move to a cloud database model, using Azure, and need an Interface Layer between these custom C++ and Java applications and the cloud storage. The cloud storage is likely PostgreSQL but is negotiable in the design process. The Interface Layer will have a well-defined API to query, access, read and write to the cloud database(s). The API will be available from C++, Java, and Python applications. The architecture must be able to locally cache data/commits in the event access to Azure is temporarily unavailable, as to not interfere with production. The data will automatically be pushed to Azure when connectivity is restored. The type of data includes traditional SQL-type record storage with several related text (~1Mb ea.) and binary (~250Mb ea.) files per device manufactured. The current total data store (SQLite databases and related files) is approximately 600Gb. Transaction frequency is relatively low; on the order of minutes during device manufacturing and fulfillment, with manufacturing periods lasting several weeks. Access concurrency is also relatively low. The API, architecture and storage model are negotiable and part of the design process.
Summary of tasks
1. Review and discuss the current requirements documentation.
2. Present a design approach for discussion and approval.
3. Implement the approved design.
4. Provide documentation for the API.
5. Migrate existing data SQLite databases to the unified cloud-based storage.
Successful applicants should ideally have:
* Proven experience in Cloud Database API development.
* Strong knowledge of PostgreSQL.
* A deep understanding of various data types and how to efficiently store and manipulate them in a database.
Only those with relevant skills and experience, apply. Please showcase your past work related to Cloud-based database projects when bidding.