Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DeepstreamHub: a faster Firebase with an open core

deepstreamhub.com

Post reply on HN
Print view View original

1–10 of 45 posts

Re: DeepstreamHub: a faster Firebase with an open core

#6

Post by marknadal »

Competitor here, please don't become an "open core" company - "Open Core" = "Crippleware".

Here is my thoughts/arguments around it, dealing with the RethinkDB and Parse shut down as well: https://hackernoon.com/the-implications-of-rethinkdb-and-par...

Plus, was invited to speak about it on the Changelog Podcast: https://changelog.com/podcast/236

Please stay truly open :) that way we can still compete. ;) Or else we'll be the only company that is fully Open Source (replication, auto failover, etc.)!

Re: DeepstreamHub: a faster Firebase with an open core

#7

Post by daveguy »

marknadal wrote: post #6

Competitor here, please don't become an "open core" company - "Open Core" = "Crippleware". Here is my thoughts/arguments around it, dealing with the RethinkDB and Parse shut down as well: https://hackernoon.com/the-implications-of-rethinkdb-and-par... Plus, was invited to speak about it on the Changelog Podcast: https://changelog.com/podcast/236 Please stay truly open :) that way we can still compete. ;) Or else we'l…

I think open core is ok. If the community is not happy with the core that is open they can fork and add their own implementation for excluded features.

Re: DeepstreamHub: a faster Firebase with an open core

#8

Post by marknadal »

daveguy wrote: post #7
marknadal wrote: post #6

Competitor here, please don't become an "open core" company - "Open Core" = "Crippleware". Here is my thoughts/arguments around it, dealing with the RethinkDB and Parse shut down as well: https://hackernoon.com/the-implications-of-rethinkdb-and-par... Plus, was invited to speak about it on the Changelog Podcast: https://changelog.com/podcast/236 Please stay truly open :) that way we can still compete. ;) Or else we'l…

I think open core is ok. If the community is not happy with the core that is open they can fork and add their own implementation for excluded features.

There was a big uproar over InfluxDB doing this "open core" (aka "Crippleware") approach: https://news.ycombinator.com/item?id=11262318 .

It isn't the right approach, and we ( http://gun.js.org ) aren't going to take it. More than happy to be the only one left standing, devoted to true open values - but I hope others join us.

Re: DeepstreamHub: a faster Firebase with an open core

#10

Post by eloff »

marknadal wrote: post #6

Competitor here, please don't become an "open core" company - "Open Core" = "Crippleware". Here is my thoughts/arguments around it, dealing with the RethinkDB and Parse shut down as well: https://hackernoon.com/the-implications-of-rethinkdb-and-par... Plus, was invited to speak about it on the Changelog Podcast: https://changelog.com/podcast/236 Please stay truly open :) that way we can still compete. ;) Or else we'l…

Leaving aside how odd it is to see a "competitor" give business model advice, open core is a perfectly fine open-source business model. Pure support based models, with very few exceptions, leave too much % of value on the table to make a strong business. Purely closed models take away too many freedoms from the customer (but can be very successful nonetheless.) Open core is a very reasonable compromise. The problem with InfluxDB is that they pulled a bait and switch - they launched looking like they were going to be fully open, and then went back on that later.

But at the end of the day any compromising on open-source ideals is going to piss someone off - heck even just choosing one OS license over another is going to piss people off. It doesn't matter. In business you need to have a thick skin to stick to your conviction about what is best for both customers and the company - whatever that may be.

Post reply on HN