Live data from Hacker News

SurrealDB: Distributed document-graph database for the realtime web

github.com

31–40 of 74 posts

Re: SurrealDB: Distributed document-graph database for the realtime web

#31
post #7

Business source license. Free for personal or commercial use. But service providers have to pay if they offer this database as a service.

Wow yeah that's true! I was interested in looking closer into Surrealdb until I noticed this.

The LICENSE file even contains the following part:

> The Business Source License (this document, or the “License”) is not an Open Source license. However, the Licensed Work will eventually be made available under an Open Source License, as stated in this License.

And README mentions nothing about FOSS/OSS, so seems the submitter here on HN added it themselves to the title. Should be removed.

Re: SurrealDB: Distributed document-graph database for the realtime web

#33

Looking through the SurrealDB website and marketing copy, I can’t help but be a little bit skeptical of the feature set [1]. Many, many smart people have burned many millions of dollars and thousands of man hours building databases claiming far fewer capabilities. Don’t get me wrong though, it would be a really awesome product with my dream feature set if they can actually pull it off. I wish them the best of luck an…

I'm going to go on a limb an guess that its performance or memory usage will be terrible compared to traditional databases

Re: SurrealDB: Distributed document-graph database for the realtime web

#35
post #25

Noob here - how do people usually assess DBs to one another? Why should I use this say over DynamoDB? Given concrete requirements or use cases it would be easier to compare given DB solutions, but when people are scoping something for say a new project, or a personal project (flexible requirements / motivation), how does that usually go down? If anyone has first hand experience on this :)

If your spec is entirely up in the air, you can start by replicating the examples. Lack of meaningful examples and/or in-depth documentation is the first red flag. You can also scan the reported issues to see if others are having trouble with core features, which is a sign of project immaturity.

Either way, it always helps to have some basic use case in mind. Bigger than "Hello, World" and smaller than a MVP. The outcome of any evaluation will heavily depend on whether it's a good fit for what you're trying to achieve.

Re: SurrealDB: Distributed document-graph database for the realtime web

#37
post #24

The websocket aspect they are working on is actually the only feature that really interests me. Direct notification from the DB on updates is insanely useful. Think of how easy it would be to build a real time app like a chat. No more long polling. No more websocket layer that polls the database.

I like this project ... but the functionality you are describing sounds like something that Postgres LISTEN/NOTIFY offers.

The value here comes from the database being able to service the websocket itself, if I read this right. So you don't have to do this in your application.

Re: SurrealDB: Distributed document-graph database for the realtime web

#38
post #27

Thanks for posting this dragonsh! I am Jaime, Founder of SurrealDB with my brother Tobie. Just the two of us at the moment but we have some some really big things planned for the database. Any feedback is really welcome! More info and can be found on a previous Hacker News post here https://news.ycombinator.com/item?id=32550543 Fireship has made two fantastic videos about SurrealDB https://www.youtube.com/watch?v=C7W…

You might know this already, but what you are creating here is future state-of-the-art.

That said, please make GraphQL and Apollo Federation support a high priority. SurrealDB could be a gamechanger but federation would allow it to be integrated into existing supergraphs, which is an enterprise requirement for adoption.

Re: SurrealDB: Distributed document-graph database for the realtime web

#39

Looking through the SurrealDB website and marketing copy, I can’t help but be a little bit skeptical of the feature set [1]. Many, many smart people have burned many millions of dollars and thousands of man hours building databases claiming far fewer capabilities. Don’t get me wrong though, it would be a really awesome product with my dream feature set if they can actually pull it off. I wish them the best of luck an…

I'm going to go on a limb an guess that its performance or memory usage will be terrible compared to traditional databases

Development velocity, however, could be off the charts with this kind of solution, as long as everything works as expected.

Re: SurrealDB: Distributed document-graph database for the realtime web

#40
post #25

Noob here - how do people usually assess DBs to one another? Why should I use this say over DynamoDB? Given concrete requirements or use cases it would be easier to compare given DB solutions, but when people are scoping something for say a new project, or a personal project (flexible requirements / motivation), how does that usually go down? If anyone has first hand experience on this :)

Not sure if relevant, but for me, when I want to develop quickly and reliably, I go with mySQL, because that's what I know best.

Then when I'm motivated, and find a DB that's really interesting, I force myself to use it (like couchDB) in order to learn my way around it.

That's how I decide what to use.

Post reply on HN