GFQL vs KatanaGraph
GFQL is a property graph database; KatanaGraph is a other database. GFQL (2023, BSD-3-Clause, Python) ranks #19 this month; KatanaGraph (2020-11, BSD-3-Clause, C++) ranks #74.
| Attribute | GFQL | KatanaGraph |
|---|---|---|
| At a glance | ||
| Rank | #19 | #74 |
| Score | 58.9 | 43.1 |
| GitHub stars | 2.6k | 104 |
| Popularity | 62.3 | 55.8 |
| Activity | 63.7 | 30.1 |
| Community | 68.8 | 30.6 |
| Research | 49.6 | 49.6 |
| Fundamentals | ||
| Description | A dataframe-native graph query language with vectorized processing and optional GPU acceleration. Supports Cypher-like syntax, embedded within the PyGraphistry library. | A graph computation library focused on parallel analytics and machine learning on large graphs. Features multithreaded execution with load balancing across multi-socket systems. |
| Vendor | Graphistry | Katana Graph |
| Model | Property Graph | Other |
| Kind | query-engine | embedded |
| Category | Growing | Emerging |
| First released | 2023 | 2020-11 |
| Status | active | inactive — Katana Graph shut down in 2023. GitHub repositories archived. |
| License | BSD-3-Clause | BSD-3-Clause |
| Written in | Python | C++ |
| Query languages | GFQL, openCypher | openCypher |
| gdotv support | no | no |
Feature scores — not surveyed for GFQL
| Feature | GFQL | KatanaGraph |
|---|---|---|
| Community & Business | ||
| Active development | — | · |
| Commercial support | — | ✓ |
| Live community | — | 0.5 |
| Open Source | — | ✓ |
| Pricing | — | ✓ |
| Trendiness | — | ✓ |
| Deployment | ||
| Containerization | — | · |
| Work as dedicated instance | — | · |
| Work as embedded | — | · |
| Testing in-memory version | — | · |
| Platform | ||
| Operating on Linux | — | ✓ |
| Operating on Windows | — | · |
| SaaS offering | — | · |
| Operations | ||
| Automatic updates | — | · |
| Client side caching | — | · |
| Data versioning support | — | · |
| Live backups | — | · |
| Distribution | ||
| Cluster Re-balancing | — | ✓ |
| Data Distribution | — | ✓ |
| High-Availability | — | · |
| Query Distribution | — | · |
| Replication support | — | · |
| Developer Experience | ||
| Data types defined | — | ✓ |
| Logging/Auditing | — | · |
| Object-Graph Mapper | — | · |
| Reactive programming | — | · |
| Documentation up-to-date | — | · |
| Binary protocol | — | · |
| CLI | — | · |
| GUI | — | · |
| Data Model | ||
| Multi-database | — | · |
| Graph-native data | — | ✓ |
| REST API | — | · |
| Query Language | — | · |
| Transactions | ||
| Granular locking | — | · |
| Multiple isolation levels | — | · |
| Read committed transaction | — | · |
| Transaction support | — | ✓ |
| Schema & Security | ||
| Constraints | — | · |
| Schema support | — | · |
| Secondary indexes | — | · |
| Server side procedures | — | · |
| Triggers | — | · |
| Authentication | — | · |
| Authorization | — | · |
| Data encryption | — | · |
Links
- GFQL · website · github · full profile
- KatanaGraph · website · github · full profile