Scorpiion

Good point, there are of course different levels.

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.

I'm curious what people think of BYOC (bring your own cloud) as an option offering to customers or buying it as a customer. Looking at Northflanks website they list it as an offering, I presume those customers are not affected by the breach.

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.

Looks like a nice service, it also sounds like something the SaaS companies who's pricing information you are showing would not like.

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).

Thanks for writing this one Simon, I read it some time ago and I just wanted to say thanks and recommend it to folks browsing the comments, it's really good!

Thanks a lot for sharing bob1029, nice explanation and justifications, much appreciated!

Hi bob1029, very interesting to hear about your experiences and point of view. Easy to forget the impact of how easy it's to sell an end product/service based on your selection of database (it does not always matter of course). I have thought about this as well, no one (?) will question if your app/service uses postgres but if you say sqlite I assume there will be some more questions.

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.

I'm not an iPhone user myself, but recently run into the fact that SwiftKey has been deprecated on iPhone when helping a friend.

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

I'm curious, what does "connector hell" mean in this context from a practical point of view?

I wonder if the decision to make all enterprise features open source was affected/influenced by the Neon release/announcement recently? The timing makes me wonder, or has this been planned for a very long time?

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.

Interesting and glad to hear, I think it makes a lot of sense in this case!

Very interesting, tempted to apply to the company as this sounds very promising and fun to work on...

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.)

FYI this is from 2018.

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

I have not used it, but my understanding is that BigQuery Omni is "BigQuery running on AWS/Azure". My understanding is that they are running Anthos on AWS (managed by Google) and they offer BigQuery as a service from that AWS infra managed by Google.

See more details here:

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

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

Does anyone know if newer Philips smart TVs have this type of ads? I have one that's around 4 years old and it doesn't have it, not sure with newer ones.

As others have mentioned there is a menu option to show the tables. You can also run this sql query to see the tables:

SELECT name FROM sqlite_master WHERE type='table'

This reminds me of Google clouds built in network firewall[1], which is just called "Google Cloud Firewalls". One difference is that Googles firewall capabilities are built in and part of the platform, no extra service or fees. Just thought it could be an interesting reference for people not so used to GCP.

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

Yeah, I did not really understand that comment either. According to the same article they had more than 1/3 of their raised funds still in the bank (1/3 of $95 million).

If anyone else is thinking, how much? I tried to do some research and I found this:

"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...

I was reading through the docs and this FAQ is worth checking out: https://github.com/canonical/dqlite/blob/master/doc/faq.md

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!

This is a good idea, I got tempted to try this. Found this page on their homepage (in Swedish): https://www.klarna.com/se/dataskydd/

Where it says you can email this address "[email protected]" if you either want them to delete your data (except data they are required to store as a bank) or if you want a print out of your personal information they store.

The matching UK site (in English) is here: https://www.klarna.com/uk/privacy-policy/ and has this email for the same purpose: "[email protected]"

Interesting, thanks for the extra info.

I just paid using their direct payment method two times the last week or so. Will be more on the lookout in the future and try to keep an eye on these things.

I tried to find more information about this statement:

"When authenticating the login you authorize one of Klarnas third parties to log into your bank account as you, allowing them to pull records of all your financial transactions, account statements etc.“

Do you have any source to verify this claim? That they can and do pull down this information. I would like to know if they really have all that information or not, if so it's a surprise to me, did not know that.

It's also worth noting that Chrome headless could be a nice alternative if you use html as the base for say invoices or reports that you want to generate from a SaaS app.

Create pdf with Chrome headless: chrome --headless --disable-gpu --print-to-pdf https://www.chromestatus.com/

Source: https://developers.google.com/web/updates/2017/04/headless-c...

Thanks for the link! =)

Ah, thanks for the links.

I googled a little bit and found some good info, I guess I had forgotten a little bit of the concepts of mutex fairness/unfairness. I found a very nice explanation on cs.stackexchange:

  "My understanding is that most popular implementations of a mutex (e.g. std::mutex in C++) do not guarantee fairness -- that is, they do not guarantee that in instances of contention, the lock will be acquired by threads in the order that they called lock(). In fact, it is even possible (although hopefully uncommon) that in cases of high contention, some of the threads waiting to acquire the mutex might never acquire it."

Source: https://cs.stackexchange.com/questions/70125/why-are-most-mu...

With that computer science clarification, I think the comment "Mutex is now more fair" and the detailed description "Unfair wait time is now limited to 1ms" makes it a lot clearer.

Great improvement I think! It's one of those things that you don't notice until you have a bug, but it's really nice to never get that bug in the first place. =)

In the release notes it says:

  "Mutex is now more fair."

Source: https://golang.org/doc/go1.9#sync

Does anyone know what that means?

Interesting to see the changes of their product packaging (and price) over time:

1. https://web.archive.org/web/20141020025157/https://www.netli...

2. https://web.archive.org/web/20160505192926/https://www.netli...

3. https://web.archive.org/web/20170221195249/https://www.netli...

4. https://www.netlify.com/pricing/

The model of charging per site was removed in [4], the "low tier" $9 per site was also removed, maybe it was not differentiated enough from the free version to be worth the effort. It also seems they introduced "paying per user" in between [3] and [4], maybe that was a form of substitute for the removal of the site limit.

Disclosure: I am a founder of a cloud hosting startup called Sourcevoid, that's in part why I think looking at pricing and packaging of hosting services is interesting, but thought others might like seeing the links above as well.

Pricing sounds so simple but it is a surprisingly complex thing to get "right". I read an article from Sequoia recently that I thought was very well written. Not sure if it's relatively new or if it's been there for ages. I recommend it anyways, great read.

# The Sequoia Guide to Pricing https://www.sequoiacap.com/article/pricing-your-product/