Very cool, keep it up. Always good to see innovations, creativity and curiosity in the database space.
SpacetimeDB
121–130 of 205 posts
Re: SpacetimeDB
#122Very cool, keep it up. Always good to see innovations, creativity and curiosity in the database space.
One question I have is what is the plan on implementing full SQL? I see currently you're only implementing maybe 15% of SQL92. Are you implementing your own SQL-like language?
Re: SpacetimeDB
#123Very cool, keep it up. Always good to see innovations, creativity and curiosity in the database space.
Another few pieces here listening to your video.
https://www.youtube.com/watch?v=kzDnA_EVhTU
You mention it runs in process? How does this occur? You mention running cached in memory tables. So you're caching on at the application level, not the storage level?
There's a few things with the video I find misleading. You mention 400ms at best to parse, plan and execute a query; That's not true, what about the type of query, etc.
Overall I can see it's still early, which is ok. I will review the code and see what else I can find.
Re: SpacetimeDB
#124Very cool, keep it up. Always good to see innovations, creativity and curiosity in the database space.
One more question I have is how are you handling the cluster architecture. I don't see that on the website. You mention on the pricing a cluster and replication but scaling horizontally is rather important and we definitely want to know how you're achieving scalability.
Re: SpacetimeDB
#125Earlier quoted context omitted.
[flagged]
I mean, they said they'd like to get your expert input on the matter. Why not give them a chance? Maybe you can help them do some much needed course correction—which is what I understood you're staying by reading a bit between the lines. Maybe you can even negotiate a consultancy fee with them You can stay sceptical, but try giving them a chance. You might end up surprising eachother! Aside: I'm getting into indie ga…
[deleted]
Re: SpacetimeDB
#126Re: SpacetimeDB
#127Earlier quoted context omitted.
I mean, they said they'd like to get your expert input on the matter. Why not give them a chance? Maybe you can help them do some much needed course correction—which is what I understood you're staying by reading a bit between the lines. Maybe you can even negotiate a consultancy fee with them You can stay sceptical, but try giving them a chance. You might end up surprising eachother! Aside: I'm getting into indie ga…
[flagged]
[deleted]
Re: SpacetimeDB
#128I wish you success! And hopefully you don't end up disappearing like SpatialOS. They tried very hard promoting its capacity for large scale MMO, even published a game (Scavenger IIRC?) made with it.
Re: SpacetimeDB
#129Earlier quoted context omitted.
[flagged]
I mean, they said they'd like to get your expert input on the matter. Why not give them a chance? Maybe you can help them do some much needed course correction—which is what I understood you're staying by reading a bit between the lines. Maybe you can even negotiate a consultancy fee with them You can stay sceptical, but try giving them a chance. You might end up surprising eachother! Aside: I'm getting into indie ga…
[flagged]
Re: SpacetimeDB
#130Earlier quoted context omitted.
When node first came out, it was pretty revolutionary. Being able to almost instantly start a JavaScript thread from a single file that could support realtime experiences (a la socket.io et al) without a build step felt pretty paradigm shifting
> could support realtime experiences Node supports realtime applications? Really? Isn't it garbage collected? Or does the term mean something different in nodejs? I've only come to know the term in the context of time guarantees (i.e. if it's scheduled to run in x, it is guaranteed to run at that time) and that shouldn't apply to nodejs I think? When you schedule something there, I believe it'll run on the first free…
Did they simply mean "non blocking?"