I was thinking of a fully private deployed within the customers cloud account connected to the software provider via Private Service Connect or PrivateLink and then either only available inside the customers private network or only via their own firewall. The point being that it's not publicly exposed.

What are your opinion on the concept? Growing trend that should be encouraged or a mistake for most startups? Would you choose one provider over the other because of it assuming price was about the same?

I get that this is often a super expensive "call us" option today, but in theory it doesn't have to be, so for the sake of discussion let's assume it can be delivered at a reasonable cost for the provider at reasonable price for the customer.

If people from Northflanks is reading this, I'm sorry for the incident and I hope you recover as soon as possible.

I'm curious how you look at that? Are there any legal risks for end users to share this type of information via your site? I'm thinking if the SaaS providers have some legal statements about not sharing prices (similar to how certain database providers don't allow sharing of database benchmarks).

Would you mind sharing some numbers of what you consider an "aggressive RPO", and what RPO number sqlite+litestream can still handle? Of course, it will depend on the use case, but if you would do a rough estimate. I think it could be helpful for a lot of readers.

Does anyone here know the details of why SwiftKey was depreciated? Did iOS change their APIs or permissions somehow or what was the reason?

https://news.ycombinator.com/item?id=31753345

Either way, great news! I've been curious to try out Citus many times but the fact that many of the best parts has been closed has held me back a bit, I think it's great with more postgresql open source extention options.

I'm curious about the business side of things, to give some context, some open source models that startups use today are:

1. The "open core" model, Gitlab being a good example. They try to split features that are open or closed/enterprise depending on the buyer.

2. The AGPL model, Mongodb used to do this, today a popular example is Grafana and their collection of products.

3. The Apache + cloud backend model, the core being standalone working with Apache license while building a value added managed service. I think this is what Synadia is doing with NATS.

4. The "source available" model, not really open source, but worth mentioning as it's very popular recently. Examples Mongodb, Elastic, Cochroachdb and TimescaleDB. This is often combined with open source such that some parts are open source, others source available.

With this as a reference Nikita, how would you explain how Neon thinks in regards to licensing and eventually building a healthy business? It's obvious a managed database service is the money maker, but how do you think around compeditors taking the project and building managed services without or with minimal code contributions? I'm sure you guys have thought a lot about this, would be interesting to hear some thoughts and reasoning for or against different options.

(Note: This is not meant to be an extensive explanation of these business models just a high level overview. If I have miscategorized some company above feel free to correct me in a comment.)

I thought it was something released recently but saw on Github that it's from 2018.

See more details here:

- https://cloud.google.com/bigquery-omni/docs/introduction

- https://cloud.google.com/bigquery-omni/docs/aws

SELECT name FROM sqlite_master WHERE type='table'

[1] https://cloud.google.com/firewalls

"The companies announced the deal Wednesday but didn’t disclose the terms. Two people familiar with the deal said SUSE is paying $600 million to $700 million."

Source: https://www.cnbc.com/2020/07/08/suse-acquires-rancher-labs.h...

Comments URL: https://news.ycombinator.com/item?id=22498005

Points: 1

# Comments: 0

In includes an answer about the difference with rqlite.

To me reading the docs it seems like dqlite has been developed by the team who develops LXD at Canonical as LXD is listed as the biggest user of the project and it says on the authors github that he works at Canonical at/with LXD/LXC.

Interesting project, good luck to the author/authors if you read this!