IT4Change/Ocelot-Social
3
0
Fork 0
mirror of https://github.com/IT4Change/Ocelot-Social.git synced 2025-12-13 07:45:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix very minor README typos or omissions

Browse Source
This commit is contained in:
Federico Esparza 2018-12-16 10:23:19 -06:00 committed by GitHub
parent 4fac6c4e5e
commit 48ced0d47c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -4,15 +4,15 @@
> This Prototype tries to resolve the biggest hurdle of connecting our services together. This is not possible in a sane way using our current approach.
>
> With this Prototype we can explore using the combination of GraphQL and the Neo4j Graph Database for achieving the connected nature of a social graph with better development experience as we do not need to connect data by our own any more through weird table structures etc.
> With this Prototype we can explore using the combination of GraphQL and the Neo4j Graph Database for achieving the connected nature of a social graph with better development experience, as we do not need to connect data on our own any more through weird table structures etc.
>
> **Advantages:**
> * easer data structure
> * easier data structure
> * better connected data
> * easy to achieve "recommendations" based on actions \(relations\)
> * more performant and better to understand API
> * better API client that uses caching
>
> We still need to evaluate the drawbacks and estimate the development cost of such an approach
> We still need to evaluate the drawbacks and estimate the development cost of such an approach.