ObjectBox Java (Kotlin, Android)
edgedb
Our great sponsors
ObjectBox Java (Kotlin, Android) | edgedb | |
---|---|---|
14 | 19 | |
4,303 | 12,236 | |
0.4% | 1.2% | |
8.3 | 9.9 | |
2 months ago | 2 days ago | |
Java | Python | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ObjectBox Java (Kotlin, Android)
-
Publishing to F-Droid
When I first attempted to publish to F-Droid, I experienced several pipeline issues. After reading through the pipeline logs in GitLab, I realized that my application's database (ObjectBox) was not entirely FOSS compliant and was causing build failures. The following day was spent migrating my app to Room.
-
Looking for android java developer mentor
I would focus on Kotlin instead of Java, there's really no point in sticking to Java at this point. And when it comes to databases, some local ones that are pretty easy to get into are Realm and ObjectBox, SQLite can definitely be a bit overwhelming at the beginning.
-
Will ObjectBox ever support AARM64 architecture for Linux machines?
Not sure what exactly the issue is in your case, but linux-aarch64 is already a supported platform for ObjectBox (with some dependencies on libc versions etc). Maybe raise an issue for https://github.com/objectbox/objectbox-java with your specific error output and some details on your setup?
-
Want to build a simple database app....Where do I start
Just to add to this, there's also Realm and ObjectBox as alternatives.
-
EdgeDB 2.0
Adding ObjectBox [0] to the list.
-
Best libraries for Android Developers
Obectbox
-
Embedded databases - What is an embedded database? and how to choose one
While - strictly speaking - "database" refers to a systematic collection of data, "Database Management System'', or DBMS, refers to the piece of software that provides an efficient and versatile method of working with data(eg: ObjectBox). However, often the term "database" is also used loosely to refer to a DBMS, and you will find most DBMS only use the term database in their name and communication.
-
Best way to store nosql data locally on Android device?
Maybe this? I've been looking at it recently.
-
Best way to pass data to a fragment and prevent Transaction Too Large exceptions?
https://github.com/objectbox/objectbox-java is an alternative to Room.
-
ObjectBox 3.0: an embedded lightweight database for (Java) objects without ORM/SQL layer
Here's the issue
edgedb
- EdgeDB – A graph-relational database with declarative schema
-
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?
-
EdgeDB 3.0
The whole thing consists of these main parts:
1. SQL parser: https://github.com/edgedb/edgedb/tree/master/edb/pgsql/parse...
-
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.
-
Question about custom properties querying with the query builder
We need to land #3747, then something like this should work
- EdgeDB 2.0
-
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 into one “… WHERE id IN (…)”. Sounds like a great use of your time.
In the end you might think to yourself “why am I doing this, when my SQL database already has query optimisation?”. And it’s a fair question, you are onto it. Try one of those auto-GraphQL things instead. EdgeDB (https://edgedb.com) does it as we speak, runs atop Postgres. Save yourself the enormous effort if you’re only building a GraphQL API for a single RBDMS, and not as a façade for a cluster of microservices and databases and external requests.
Or just nod to your boss and go back to what being a backend developer has always meant: laboriously building by hand completely ad hoc JSON versions of SQL RBDMS schemas, each terribly unhappy in its own way. In no way does doing it manually but presenting GraphQL deviate from this Sisyphean tradition.
I read in the article that NOT having GraphQL exactly match your DB schema is a best practice. My response is “did a backend developer write this?”
-
How we sharded our test suite for 10x faster runs on GitHub Actions
Same idea, yeah. Unfortunately, in our case we couldn't use pytest due to complicated test setup, so we used a customized unittest runner instead.
-
GraphQL is now available on Supabase
EdgeDB [1] has indeed a rich GraphQL layer, but it's a very different project.
While it also builds on top of Postgres, EdgeDB replaces the entire relational database front-end. EdgeDB features a SQL replacement language called EdgeQL (analytical capabilities of SQL married with deep-fetching in GraphQL), a higher-level data model (tables -> object types), integrated migrations engine, a custom protocol with great performance & great client APIs, and many other things. Read more here [2].
(disclaimer: I'm EdgeDB co-founder)
-
EdgeDB 1.0
I'm curious how this squares up with what someone linked elsewhere: https://github.com/edgedb/edgedb/discussions/3403
> EdgeDB does not treat Postgres as a simple standard SQL store. The opposite is true. To realize the full potential of the graph-relational model and EdgeQL efficiently, we must squeeze every last bit of functionality out of PostgreSQL's implementation of SQL and its schema.
This would seem to be an opposing view of how coupled EdgeDB and PostgreSQL are. Which is it?
What are some alternatives?
Apache Hive - Apache Hive
supabase - The open source Firebase alternative.
cockroach - CockroachDB - the open source, cloud-native distributed SQL database.
SQLDelight - SQLDelight - Generates typesafe Kotlin APIs from SQL
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, branching, and bottomless storage.
Nitrite Database - NoSQL embedded document store for Java
Prisma - Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB
RxDB - A fast, local first, reactive Database for JavaScript Applications https://rxdb.info/
supabase-graphql-example - A HackerNews-like clone built with Supabase and pg_graphql
RoomAsset - A helper library to help using Room with existing pre-populated database [DEPRECATED].
edgedb-rust - The official Rust binding for EdgeDB