Announcing SurrealDB 1.0
surrealdb.com
Announcing SurrealDB 1.0
1–10 of 56 posts
Re: Announcing SurrealDB 1.0
#2> Imagine a world where the majority of your backend logic is seamlessly embedded within the database itself
thinks of Oracle APEX
thinks of IBM AS400
shudders
Re: Announcing SurrealDB 1.0
#3Fireship did a 'SurrealDB in 100 seconds' in case anyone would like a quick video summary: https://youtu.be/C7WFwgDRStM?si=va17q7zagn4lIoi3
Re: Announcing SurrealDB 1.0
#4I like where they are going. Are there benchmarks out yet?
Re: Announcing SurrealDB 1.0
#5Not Open Source (in an OSI way):
https://github.com/surrealdb/surrealdb/blob/ed60a35b9b539e1b...
Re: Announcing SurrealDB 1.0
#6My biggest concern with SurrealDB is the license, otherwise I'd be very interested in adopting it.
I know the license is okay, but from my reading of it, sounds like if SurreaDB really wanted to shut you down they could.
Otherwise, I find the architecture of it to be beautiful and compelling.
Re: Announcing SurrealDB 1.0
#7Not Open Source (in an OSI way): https://github.com/surrealdb/surrealdb/blob/ed60a35b9b539e1b...
Is it claiming anywhere to be open source? I've heard an interview with the creators and they seemed pretty open about which aspects where open source and which aspects where shut down?
I could be missing something from their branding but I'd rather see projects with non-open source licenses from the beginning that bait-and-switch license change when they want to become profitable. (Although, I'd much rather just see a fully open source project)
Re: Announcing SurrealDB 1.0
#8My biggest concern with SurrealDB is the license, otherwise I'd be very interested in adopting it. I know the license is okay, but from my reading of it, sounds like if SurreaDB really wanted to shut you down they could. Otherwise, I find the architecture of it to be beautiful and compelling.
Unless you're operating a "database service", a well defined term (in the license) that excludes almost every use-case
A “Database Service” is a commercial offering that
allows third parties (other than your employees and
contractors) to access the functionality of the
Licensed Work by creating tables whose schemas are
controlled by such third parties.
Re: Announcing SurrealDB 1.0
#9It benches very very slow and no options to horizontally scale outside of manual sharding.
API has a cool design though.
The dev team needs to look at perf before the complexity hole gets too insane if it hasn't already.
Re: Announcing SurrealDB 1.0
#10It benches very very slow and no options to horizontally scale outside of manual sharding. API has a cool design though. The dev team needs to look at perf before the complexity hole gets too insane if it hasn't already.
What’s your source on the benchmark thing? It seems like they have a lot of backend KV store options including FoundationDB and TiKV which are both distributed, so I’d be curious how the backends perform relative to one another.