Neptune vs ZipG
Neptune is a multiple database; ZipG is a other database. Neptune (2017-11, Proprietary, C++) ranks #14 this month; ZipG (2017, C++) ranks #83. They differ on 33 of 46 surveyed features.
| Attribute | Neptune | ZipG |
|---|---|---|
| At a glance | ||
| Rank | #14 | #83 |
| Score | 61.1 | 40.3 |
| GitHub stars | — | 13 |
| Popularity | 61.0 | 34.0 |
| Activity | 60.9 | 37.4 |
| Community | 61.8 | 49.3 |
| Research | 60.4 | 53.0 |
| Fundamentals | ||
| Description | A fully managed graph database service from AWS supporting both property graph and RDF models. Available as Neptune Database (for transactional workloads) and Neptune Analytics (for analytical queries). | A research prototype graph store that executes queries directly on a compressed graph representation for memory efficiency. Lacks traditional database features such as transactions and replication. |
| Vendor | Amazon Web Services | — |
| Model | Multiple | Other |
| Kind | database | embedded |
| Category | Enterprise | Emerging |
| First released | 2017-11 | 2017 |
| Status | active | inactive — Academic research prototype from AMPLab Berkeley. No active development. |
| License | Proprietary | — |
| Written in | C++ | C++ |
| Query languages | Gremlin, SPARQL, openCypher | Custom API |
| gdotv support | yes | no |
Feature scores 33 of 46 rows differ
| Feature | Neptune | ZipG |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | · |
| Commercial support | ✓ | · |
| Live community | ✓ | · |
| Open Source | · | ✓ |
| Pricing | ✓ | · |
| Trendiness | ✓ | · |
| Deployment | ||
| Containerization | · | · |
| Work as dedicated instance | ✓ | ✓ |
| Work as embedded | · | · |
| Testing in-memory version | · | · |
| Platform | ||
| Operating on Linux | ✓ | ✓ |
| Operating on Windows | · | 0.75 |
| SaaS offering | ✓ | · |
| Operations | ||
| Automatic updates | ✓ | · |
| Client side caching | ✓ | · |
| Data versioning support | · | · |
| Live backups | ✓ | · |
| Distribution | ||
| Cluster Re-balancing | · | · |
| Data Distribution | · | ✓ |
| High-Availability | ✓ | · |
| Query Distribution | 0.5 | ✓ |
| Replication support | ✓ | · |
| Developer Experience | ||
| Data types defined | 0.5 | 0.5 |
| 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 | 0.5 | · |
| Secondary indexes | ✓ | · |
| Server side procedures | · | · |
| Triggers | · | · |
| Authentication | ✓ | · |
| Authorization | ✓ | · |
| Data encryption | ✓ | · |
Links
- Neptune · website · full profile
- ZipG · github · full profile