Google Git
Sign in
apache / age / refs/heads/PROPOSAL_API_Server
commitdc40b4421a8edd06f4cf457dd636002edb2df50d[log] [tgz]
authorMorpheus <85464872+yjy44@users.noreply.github.com>Tue May 07 07:35:15 2024 +0900
committerGitHub <noreply@github.com>Mon May 06 15:35:15 2024 -0700
treecb9308072f43d13df93e7d773c43ef70c2d069e7
parentdae205025ead04d854a6e5db890b32f69d574d90 [diff]
[PROPOSAL] Committed initial folder and Architecture of API-Server (#1828)

* AGE Code Cleanup

* Add initial versions and initial architecture of API-Server
13 files changed
tree: cb9308072f43d13df93e7d773c43ef70c2d069e7
  1. architecture/
  2. assets/
  3. cli/
  4. community/
  5. docker-compose/
  6. docs/
  7. frontend/
  8. img/
  9. packaging/
  10. scripts/
  11. server/
  12. translations/
  13. README.md
README.md

This Project is an API that executes queries in Cypher or Graph QL format on RDBs such as PostgreSQL, Oracle, and MySQL and returns the results to the user in the form of the requested query.

At this time, through AGE Storage, integrated metadata can be managed regardless of RDB type such as Oracle, MySQL, and MSSQL, and data query is supported through Open Cypher/GraphQL without the need to change the core at the RDB level. It can also provide usefulness in terms of analysis through result visualization tailored to Open Cypher/GraphQL.

Currently, this Project will develop :

  • Meta Data Generator : After connection, table is converted to node and
    1. created / edge is created based on constraints
    2. Part that implements logic to check update information when a connection exists
    3. Metadata management (select only desired tables) Must be managed by graph
  • Query Modifier : R&D on query conversion unit in progress
    1. Cypher -> Target DB Query conversion
    2. GraphQL -> Target DB Query conversion
    3. Identify and preserve target DB type
    4. Created Query and Cypher/GraphQL mapping management function
  • Return Caster : A part that implements the function of converting data received through a query converted from the Query Modifier to fit the initially requested form.

We plan to develop it on a web basis, and it will be based on the contents below.

  1. UI support and advancement for connection and query conversion functions
  2. Enhanced connection data front logic
  3. Add Query Modifier related interface
  4. Apply Return Casting result UI