by jaimemh on 9/17/22, 7:11 AM
by user1029384756 on 9/17/22, 5:35 AM
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 and it will be very interesting see where SurrealDB ends up in a few years time!
[1] https://surrealdb.com/why
by habibur on 9/17/22, 5:12 AM
Business source license.
Free for personal or commercial use. But service providers have to pay if they offer this database as a service.
by tluyben2 on 9/17/22, 9:27 AM
This sounds like great work; been playing with graph dbs lately and it makes things easier. I was hoping though that there would be an effortless offline component to it though; maybe I missed it but there seems to be none? We have been trying to find a replacement for couch/pouch which gives the same convenience as that combo (besides setting up the right filters and permissions, everything works automatically). I see many people rolling (usually very hacky ‘cache invalidation’) solutions which require a lot of domain knowledge where pouch just works and querying server and client (mostly) the same way also lightens the load a lot. Couch is old and works very well, but, besides being very good at synching, it has a lot of downsides which we just ignored (which worked for us for a decade and very well at that), but with we are not good with couch (erlang) as rust/go/ts team and with the advances in webasm and anything-to-js, as well as having bucketloads of memory and storage on most non-iot (but even some of those if done with care) edge devices these days, you would think there would be a solution that allows me to do this outside couch/pouch. Of course here I forget to mention; although we would not mind paying for it, it needs to have an actual OSS license (not open core but apache/mit/bsd or whatnot). And yes, we might have a go at it ourselves but we are swamped at the moment.
Edit; the project has ‘eventual FOSS’ which I like as a concept and thought of doing myself; put milestones in place which can be externally verified which will trigger the license of the (semi) closed product to become fully foss.
by iddan on 9/17/22, 5:24 AM
by wrbl on 9/17/22, 7:57 AM
by revskill on 9/17/22, 6:15 AM
This is really perfect ORM layer i'm looking for (mostly because of scalability and embeded JS capability). Thanks!
Wish postgresql could push embeded JS to the extreme.
by manifoldgeo on 9/17/22, 5:36 AM
This title sounds like a buzzphrase generated by GPT-3 if it were fed a corpus of nothing but HN titles. I haven't actually read the article, but the only way it could sound more like an HN post is if it mentioned Nix.
This isn't so much a value judgement as it is an observation.
by maxpert on 9/17/22, 6:14 AM
I've been down this road multiple times with Arango DB, and Orient DB and IDK how many others. Doing too much of everything usually means not good at everything. I will stick to doing one job good, and battle tested tools.
by varorav on 9/17/22, 7:03 AM
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 :)
by resoluteteeth on 9/17/22, 4:33 AM
The "What is SurrealDB" page says "with support for... full-text indexing" which implies that SurrealDB has that now, but the features page lists "Full text indexing and filtering" as "future"
I would suggest changing the description to better distinguish between what's currently available and what's a future plan to match the features page.
by Jedd on 9/17/22, 5:26 AM
by bufferoverflow on 9/17/22, 6:42 AM
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.
by dustedcodes on 9/17/22, 10:41 AM
by dariosalvi78 on 9/17/22, 1:07 PM
cool project, reminds me a bit of arangoDB, but here even more logic can be built into SQL, allowing to develop (almost) the whole backend logic into the DB. The main problem with this kind of technology is that you move logic from established programming languages (java, C#, go, ...) to something more exotic which only a few programmers know. The other problem is lock-in, if the project dies you have to rewrite all your backend.
I wish you success though, to the point where those issues I mentioned are no longer true.
by metadat on 9/17/22, 3:53 AM
Does is support Cypher?
by IceDane on 9/17/22, 11:09 AM
I really hope this, or something like it, ends up succeeding massively. Someone needs to put a bullet in SQL so that we can innovate properly in this space.
by lakomen on 9/17/22, 12:06 PM
Ok I read more about it and I agree with the sentiment.
But...
I have a project I've been planning in mind for a while, I'd like to use it for this.
There is no documentation.
by truth_seeker on 9/17/22, 8:04 AM
by AhmadIbrahim on 9/17/22, 4:39 PM
I really need this to take off and be as good as advertised! I can't afford the risk of being an early adopter tho.
by magundu on 9/17/22, 4:38 AM
Does it similar to supabase?
Any big difference between them?
Please don’t include “built on Rust”.
by johnwoods on 9/17/22, 9:39 AM
That's a hell lot of buzzwords (GPT-3 trained with HN titles, eh?). Does "serverless" and "cloud-native" database together even make any sense? Idk, but I feel like these folks are doing too much pointless marketing when the core product literally just "borrows" code from other databases without any credit to them.
Came across this rather interesting issue on their own repo: https://github.com/surrealdb/surrealdb/issues/103
I think it's time we say "Stable Diffusion Powered Hyperfast Scalable Ultimate Cloud-Native Kubernetes Native Document Graph Relational NewNoSQL Database"
Enough of the buzzwords on HN, honestly. Also, NOT FOSS.
by PeterZaitsev on 9/17/22, 7:16 PM
Great idea. Too bad it is not Open Source
by setij on 9/17/22, 6:27 AM
Tfnylb3544_