Show HN: CursusDB – A new scalable distributed document oriented database
1–10 of 70 posts
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#2I'm free to answer any questions any of you may have!
Also,
https://www.youtube.com/watch?v=UHZ42NkN1OQ https://www.youtube.com/watch?v=n1t5Iexx4UY I've put lot's of effort into the documentation and continuously try to perfect it!
https://cursusdb.com/documentation
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#3For new products I always recommend the same thing: name your competitors and use cases. Compare them in a table; don't make the user think. Who should and should not use your product? Being in-memory and distributed, I imagine your competitors include Ignite and Hazelcast?
I read the title as CursorDB, which would have made a nice DB name.
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#4For new products I always recommend the same thing: name your competitors and use cases. Compare them in a table; don't make the user think. Who should and should not use your product? Being in-memory and distributed, I imagine your competitors include Ignite and Hazelcast? I read the title as CursorDB, which would have made a nice DB name.
Good point, my first thought is, why wouldn't I just use Couchbase? It is proven and has a community around it.
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#5For new products I always recommend the same thing: name your competitors and use cases. Compare them in a table; don't make the user think. Who should and should not use your product? Being in-memory and distributed, I imagine your competitors include Ignite and Hazelcast? I read the title as CursorDB, which would have made a nice DB name.
Hi esafak. I don't really care for competitors. In regards to use cases there are so many! Currently I am working on few tutorials on how to build different applications like a Hackernews clone with a real-time frontend. These tutorials are to bring light to the functionalities of the database and give users ideas. Yeah I don't know those companies, nor do I care to. I built and designed the database the way I wanted to use a database, simple as that. I have my own use cases for a transactional email service relaying what comes through an Observer to client webhooks for example.
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#6For new products I always recommend the same thing: name your competitors and use cases. Compare them in a table; don't make the user think. Who should and should not use your product? Being in-memory and distributed, I imagine your competitors include Ignite and Hazelcast? I read the title as CursorDB, which would have made a nice DB name.
Cursus means course in Latin. The database is distributed by nature. Cluster routes data etc. You can piece it together.
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#7For new products I always recommend the same thing: name your competitors and use cases. Compare them in a table; don't make the user think. Who should and should not use your product? Being in-memory and distributed, I imagine your competitors include Ignite and Hazelcast? I read the title as CursorDB, which would have made a nice DB name.
Hi esafak. I don't really care for competitors. In regards to use cases there are so many! Currently I am working on few tutorials on how to build different applications like a Hackernews clone with a real-time frontend. These tutorials are to bring light to the functionalities of the database and give users ideas. Yeah I don't know those companies, nor do I care to. I built and designed the database the way I wanted…
You have competitors whether you like it or not -- unless you don't care for users, either. A sibling commenter asked "Why not just use Couchbase?" If your answer is "figure it out yourself; I already wrote documentation" you are shooting yourself in the foot. Documentation is not marketing. Marketing means helping potential users understand why they should use your product rather than something similar.
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#8For new products I always recommend the same thing: name your competitors and use cases. Compare them in a table; don't make the user think. Who should and should not use your product? Being in-memory and distributed, I imagine your competitors include Ignite and Hazelcast? I read the title as CursorDB, which would have made a nice DB name.
Good point, my first thought is, why wouldn't I just use Couchbase? It is proven and has a community around it.
I don't like MongoDB or Couchbase. I dislike their query languages and designs in general. I built the DB for my own liking and use cases. If others like it that's great, if not it doesn't hurt me. I made it open source to follow the process and I'm not looking for any profit or gain for doing any of it. I'd like honest opinions obviously but that's all. Eventually if people really like the DB and it requires ALL my time then I'll try to expand on the cloud offering because I am mighty passionate about the project and want to see it being used as much as possible and easily as possible!
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#9Earlier quoted context omitted.
Hi esafak. I don't really care for competitors. In regards to use cases there are so many! Currently I am working on few tutorials on how to build different applications like a Hackernews clone with a real-time frontend. These tutorials are to bring light to the functionalities of the database and give users ideas. Yeah I don't know those companies, nor do I care to. I built and designed the database the way I wanted…
You have competitors whether you like it or not -- unless you don't care for users, either. A sibling commenter asked "Why not just use Couchbase?" If your answer is "figure it out yourself; I already wrote documentation" you are shooting yourself in the foot. Documentation is not marketing. Marketing means helping potential users understand why they should use your product rather than something similar.
I agree. I very much care for the users of the database because their experience if everyone elses in a way. My reply was pretty simple lol. You build something YOU like and have a need for there's a chance others will as well. If you just build something that you don't like and have no need for, others probably wont as well.
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#10For new products I always recommend the same thing: name your competitors and use cases. Compare them in a table; don't make the user think. Who should and should not use your product? Being in-memory and distributed, I imagine your competitors include Ignite and Hazelcast? I read the title as CursorDB, which would have made a nice DB name.
Hazelcast seems like Redis. CursusDB is more like MongoDB I'd say in comparison.