Google Cloud Datastore VS EdgeDB

Compare Google Cloud Datastore VS EdgeDB and see what are their differences

Unimus

Unimus is a Network Automation and Configuration management (NCM) solution designed for fast deployment network-wide and ease of use. Unimus does not require learning any abstraction or templating languages, and does not require any coding skills. sponsored

Contents:

» Base Details
» Videos
» Reviews
» Alternatives

Google Cloud Datastore

Cloud Datastore is a NoSQL database for your web and mobile applications.

EdgeDB

EdgeDB is a next-generation graph-relational database that lets you easily build flexible, scalable applications in real-time.

Landing page //
2023-09-12

Landing page //
2023-10-10

Google Cloud Datastore

Website: cloud.google.com
$ Details

Edit details

EdgeDB

Website: edgedb.com
$ Details

Edit details

Google Cloud Datastore features and specs

Scalability
Google Cloud Datastore can automatically scale to handle large amounts of data and high read/write loads, making it suitable for applications with growing data needs.
Fully Managed
As a fully managed service, Google Cloud Datastore eliminates the need for managing servers, software patches, and replication, allowing developers to focus on building applications.
High Availability
Datastore provides strong consistency for reads and writes and is designed to maintain availability even in case of entire data center outages.
Flexible Data Model
The schemaless nature of Datastore allows for a flexible data model that can easily adapt to changes in application requirements.
Integration with Google Cloud Platform
Datastore seamlessly integrates with other Google Cloud Platform services, which simplifies the process of building end-to-end solutions.

Possible disadvantages of Google Cloud Datastore

Complex Query Language
Datastore Query Language (GQL) can be less intuitive compared to SQL, which may pose a learning curve for developers accustomed to traditional relational databases.
Eventual Consistency for Queries
While Datastore offers strong consistency for entity lookups by key, queries must be specifically configured for strong consistency, otherwise they might return eventually consistent data.
Cost
As usage scales, costs can increase, particularly for applications with high write loads or those requiring many transactional operations, which might be a consideration for budget-conscious projects.
Limited Relational Capabilities
Datastore is a NoSQL database, which means it lacks some of the relational features like joins and complex transactions that developers might expect from a SQL database.
Index Management
Managing indexes can become complex, as every query in Datastore requires a corresponding index, and poorly planned indexes can lead to increased storage costs and slower query performance.

EdgeDB features and specs

Graph-Relational Model
EdgeDB combines the features of relational and graph databases, allowing for complex queries and relationships while maintaining data integrity typical in relational databases.
Advanced Query Language (EdgeQL)
EdgeQL offers a more intuitive and expressive query syntax compared to traditional SQL, facilitating easier and more efficient data retrieval.
Schema Evolution
EdgeDB provides robust tools for schema migrations and versioning, making it easier to evolve the database schema without downtime or data loss.
Type Safety
With its strong typing system, EdgeDB reduces runtime errors by ensuring data type consistency across the database operations.
Integrated Indexing and Constraints
EdgeDB supports advanced indexing and constraints, improving query performance and maintaining data integrity natively.

Possible disadvantages of EdgeDB

Relative Newness
Being relatively new in the market, EdgeDB might lack extensive community support and third-party integrations compared to more established databases.
Learning Curve
Technicians accustomed to traditional SQL or other database paradigms might face a learning curve when adapting to EdgeDB's unique features and query language.
Limited Ecosystem
EdgeDB's ecosystem, including tooling, documentation, and community resources, is less mature compared to other well-established database systems.
Potential for Rapid Changes
As a developing technology, EdgeDB may undergo rapid changes and updates, which may lead to instability or additional maintenance overhead.
Hosting and Compatibility Concerns
Deploying EdgeDB might have specific hosting requirements, and compatibility with existing infrastructure could be a concern for some users.

Google Cloud Datastore videos

No Google Cloud Datastore videos yet. You could help us improve this page by suggesting one.

Add video

EdgeDB videos

+ Add

Checking out EdgeDB - The Developer Database (Better than Prisma ORM?!)

Category Popularity

0-100% (relative to Google Cloud Datastore and EdgeDB)

Google Cloud Datastore

EdgeDB

Databases

54 54%

Databases

46% 46

NoSQL Databases

54 54%

NoSQL Databases

46% 46

Network & Admin

55 55%

Network & Admin

45% 45

Business & Commerce

100 100%

Business & Commerce

0% 0

User comments

Share your experience with using Google Cloud Datastore and EdgeDB. For example, how are they different and which one is better?

Social recommendations and mentions

Based on our record, Google Cloud Datastore should be more popular than EdgeDB. It has been mentiond 7 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

Google Cloud Datastore mentions (7)

Using Google Cloud Firestore with Django's ORM
A long time ago, a fork of Django called “Django-nonrel” experimented with the idea of using Django’s ORM with a non-relational database; what was then called the App Engine Datastore, but is now known as Google Cloud Datastore (or technically, Google Cloud Firestore in Datastore Mode). Since then a more recent project called "django-gcloud-connectors" has been developed by Potato to allow seamless ORM integration... - Source: dev.to / over 2 years ago
How to deploy flask app with sqlite on google cloud ?
In that case use Cloud Datastore (aka Firestore in Datastore Mode). It's a NoSQL db that was initially targeted just for GAE (you needed to have a GAE App even if empty to use it) but that requirement has been relaxed. Source: over 3 years ago
Is Cloud Run a good choice for a portfolio website?
As u/SierraBravoLima said - If you don't really need containerization, you can go with Google App Engine (Standard). If you need to store data, GAE will work with cloud datastore which has a large enough free tier. Source: over 4 years ago
Help! Difference between native and datastore
Datastore mode had its start in App Engine's early days (launched in 2008), where its Datastore was the original scalable NoSQL database provided for all App Engine apps. In 2013, Datastore was made available all developers outside of App Engine, and "re-launched" as Cloud Datastore. In 2014, Google acquired Firebase for its RTDB (real-time database). Both teams worked together for the next 4 years, and in 2017,... Source: over 4 years ago
I'm a dev ID 10 T please help me
Database: datastore should be very cheap, or you could just output as csv text and copy into Google Sheets (free!). Source: over 4 years ago

EdgeDB mentions (4)

Beyond SQL: A relational database for modern applications
A new DB, with a new query language that's like "SQL done right"? This immediately reminded me of EdgeDB: https://edgedb.com/ Is there anyone here who knows enough about these two products to do a compare/contrast? - Source: Hacker News / almost 3 years ago
Beyond SQL: A relational database for modern applications
See also https://edgedb.com/ which is another relational database without sql. - Source: Hacker News / almost 3 years ago
DuckDB 0.8.0
>relational no-sql Do you mean something like edgeDB?[0] Or do you mean some non-declarative language completely? I don't see the latter making much sense. The issue with SQL for me is the "natural language" which quickly loses all intended readabilty when you have SELECT col1, col2 FROM (SELECT * FROM ... WHERE 1=0 AND ... Which is what edgeDB is trying to solve. [0]https://edgedb.com/. - Source: Hacker News / about 3 years ago
GraphQL Is a Trap?
You have to do your own optimiser to avoid, for instance, the N+1 query problem. (Just Google that, plenty of explanations around.) Many GraphQL frameworks have a “naive” subquery implementation that performs N individual subqueries. You either have to override this for each parent/child pairing, or bolt something on the back to delay all the “SELECT * FROM tbl_subquery WHERE id = ?” operations and convert them... - Source: Hacker News / over 4 years ago