Show HN: CursusDB – A new scalable distributed document oriented database
41–50 of 70 posts
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#42Re: Show HN: CursusDB – A new scalable distributed document oriented database
#43"When it starts to fail, please don't curse us."
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#44"When it starts to fail, please don't curse us."
I’d say it leaves you cursed with joy but I may be biased as I created it. I really like the name Cursus and I found it one day just translating English to Latin, just randomly and really liked the meaning of it and it’s super easy to remember so I kept it in my back pocket until I had something to use it for and when designing CursusDB it sprung up whilst drawing out the initial algorithms.
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#45Wow.
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#46Earlier quoted context omitted.
I’d say it leaves you cursed with joy but I may be biased as I created it. I really like the name Cursus and I found it one day just translating English to Latin, just randomly and really liked the meaning of it and it’s super easy to remember so I kept it in my back pocket until I had something to use it for and when designing CursusDB it sprung up whilst drawing out the initial algorithms.
It is a good name. I'm just working on taglines for you. ;-)
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#47Of course there are many ways to skin a cat, this seems like a very odd choice for organizing a database codebase. Some of the methods like cluster.HandleClientConnection() are crazy long for loop + if/else + switch + goto!
I know that you've said this is just kind of in your best interests codebase, but if I was planning on making any sort of dependencies on this project, I'd probably shy away from it because it seems like unmanageable spaghetti.
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#48Interesting product. I'm reading through the source and... Woah... it is all in one single file with zero unit tests. Of course there are many ways to skin a cat, this seems like a very odd choice for organizing a database codebase. Some of the methods like cluster.HandleClientConnection() are crazy long for loop + if/else + switch + goto! I know that you've said this is just kind of in your best interests codebase,…
It's not even 3,000 lines. That's not a lot of spaghetti.
cluster.HandleClientConnection looks like a standard network service event loop, except the code is inline instead of spread across cluster.HandleSyncData, .HandleDelete, etc.
The lack of tests though...
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#49Interesting product. I'm reading through the source and... Woah... it is all in one single file with zero unit tests. Of course there are many ways to skin a cat, this seems like a very odd choice for organizing a database codebase. Some of the methods like cluster.HandleClientConnection() are crazy long for loop + if/else + switch + goto! I know that you've said this is just kind of in your best interests codebase,…
Re: Show HN: CursusDB – A new scalable distributed document oriented database
#50Interesting product. I'm reading through the source and... Woah... it is all in one single file with zero unit tests. Of course there are many ways to skin a cat, this seems like a very odd choice for organizing a database codebase. Some of the methods like cluster.HandleClientConnection() are crazy long for loop + if/else + switch + goto! I know that you've said this is just kind of in your best interests codebase,…
> unmanageable spaghetti. It's not even 3,000 lines. That's not a lot of spaghetti. cluster.HandleClientConnection looks like a standard network service event loop, except the code is inline instead of spread across cluster.HandleSyncData, .HandleDelete, etc. The lack of tests though...