Local Database hosting

Our product will be a service that will resolve a few major issues faced by developers while development time and provide some features. Resolving the issue which is faced while achieving the service of a shared database, which can be shared among the whole team. R

Project Title

Local Database hosting

Project Area of Specialization

Computer Science

Project Summary

Our product will be a service that will resolve a few major issues faced by developers while development time and provide some features.

• Resolving the issue which is faced while achieving the service of a shared database, which can be shared among the whole team.

• Resolving the issues of  managing access and monitoring and controlling the access of database and other resoruces.

• Resolving the need to create a node js API for accessing the Mysql database in mobile applications.

Since there are many solutions for achieving these features.

• One solution is to use an online paid service

• Second is to use an online free service

• hird is to configure the localhost to be accessed from anywhere since this has some security concerns and it is limited

  • It does not provide suitable features for team-based environments

While using either of these solutions, there are a few factors that cause hindrance to using them.

1. One identified factor is the cost factor since online paid services are expensive

2. if we ignore the cost and use online free services then those are very limited in terms of access to resources and time period.

3. The third factor, while using the method of configuring the local host, is that it is very hard and complicated to set-up. Along with this it brings some security concerns as well like exposing IP addresses to 3rd parties. 

Hence our our proposed solution is providing solutions to these factors/problems. Our product will be resolving the above highlighted factors. Cost factor will be resolved because our product will be utilizing the local database. Second factor, of the dashboard to manage the sharing of databases among team based environments,  will be resolved because we will be providing such a dashboard. And security concerns will be resolved in the way that we are introducing and using a new authentication scheme which will be using email and token for identification instead of using IP.

Project Objectives

We have identified a few common problems and some concerns which will be the core objectives of our product. Following is the list of identified problems and concerns.

1. Reduce complexities while configuring localhost to be accessed from the internet. Along with providing features of access control for using the local database as a shared among the team.

2. Reducing the cost factor by providing a service.

3. Resolving the issue faced while using free online web services like limited resources.

4. Resolving the security concerns, like exposing IP addresses to 3rd party service, faced while using existing solutions.

Project Implementation Method

The implementation process will be based on multiple phases. In each phase at least one required feature will be designed and implemented. Following is the list of phases which are shown on an abstract level how we will achieve the final product.

1. In the first phase, we will design and define the core components of complete architecture with all detailed documentation

2. In this phase, based GUIs will be designed and developed so that rest of the next components could be tested and developed, and observed properly. Along with GUI, we will create an API interface using SWAGGER for test inputs and outputs.

3. In this phase, the target will be to design and develop a complete request management system having attributes of a fine-grained access control system for both layers discussed above.

4. In this phase, the target will be to design and develop a query text processing and formatting engine for both types of mentioned layers in the above sections. 

5. The purpose of this phase will be to design and develop a system that will be responsible for sending and receiving data to and from our central API. This system will involve the implementation of push notifications.

6. After the above phases, we will update the request management system by integrating a component that will be responsible for adding the functionality of queuing on the central API and the other two layers.

7. The purpose of this phase will be to develop the log monitoring system along with the interface, for integrating into the central API, and database configuration interface, for integrating with the end-user and central API connecting layer.

8. After this phase, we will update the previous phase to make a complete web-based admin portal.

9. In this phase, we will develop an authentication scheme and user accounts management system along with screens and back-end work. This whole phase will be implemented on the central API and the other two layers.

10. After this phase, a complete suite for using the product, a few npm packages, and a few java libraries will be written.

Benefits of the Project

Following are the major benefits of our product. 

Note : (for first version we are working on database resource) 

1. It allows the local resources to be used as hosted.

2. It provides you full control over your shared resources ( Database ).

3. It resolves the threat of exposing your IP address.

4. It resolves the need to create and host an node js APIs, which have only basic and common operations, for accessing databases in mobile applications or web application 

Technical Details of Final Deliverable

The architecture of our product will be divided into three main parts. One part will be a central online hosted web app and the rest of the two parts will be connecting layers. One layer will be responsible for connecting the host computer to the central API and managing the requested input of our output queries sent by the central API to this layer for manipulating the database and sending responses back to our central API. The second layer will be responsible for connecting the end-users to the central API and managing sent input queries and receiving out responses in end-user applications. For a better understanding of the structure and placement of layers and other details refer to the following diagram.

Since central API architecture will be providing a bunch of features. For example, it will be providing a complete admin portal for managing the roles of teams and other limits on the resource (database) shared along with a log. Along with this, both layers will be specially designed along with features like a fine-grained access control system (FGAC System) for managing the incoming and outgoing requests from and towards the central API. These layers and the central API architecture will implement a requests management system that will involve a specially designed heap pool along, having a query text processing and formatting engine for formatting the requests. Along with these layers will process the requests without asking for some crucial credentials like in setting up a server we need to change firewall security or allow the third part to detect our IP address, in case we are using free DNS service. Our product architecture will be using a token-based authentication system for avoiding security concerns and will provide a controller interface for managing access and monitoring functionality.

Final Deliverable of the Project

Software System

Core Industry

IT

Other Industries

Core Technology

Cloud Infrastructure

Other Technologies

Sustainable Development Goals

Industry, Innovation and Infrastructure

Required Resources

If you need this project, please contact me on contact@adikhanofficial.com