gwen-shapira

6 ms·

31.
by gwen-shapira 3y ago
It is a Postgres, so schema and migrations work exactly as they would elsewhere. Tenants are your customers. It is normal for SaaS to have either a schema per tenant or one schema and tenant_id column in most tables. Nile provides you with
32.
by gwen-shapira 3y ago
Ooh, yes! I need to get a Django and other Python examples going. With Flask it is fairly straightforward - you add the tenant configuration to the DB connection when you pick it up to serve a request. The Java and NodeJS examples do someth
33.
by gwen-shapira 3y ago
great point! If they travel a lot, you may want the data in one location (although it still depends, moving data is often faster than flying to a different region). Tenant placement is especially great if their location has data residency r
34.
by gwen-shapira 3y ago
Nile co-founder here :) Nice surprise to see our launch here. Happy to answer any questions...
35.
by gwen-shapira 3y ago
Gwen here. Just wanted to mention how awesome Andy is. I haven't yet read his book, but as a senior developer - he has this great combination of wide domain knowledge, wide experience and very practical approach. It is so good to talk
36.
by gwen-shapira 3y ago
Maybe worth pointing out the original interview (it is in a follow up tweet as well) and the blog posts that lead to it. There are so many more details. I especially love the improvements that Vignesh and his team made to pgBouncer. Being a
37.
Navigating IO Issues in Cloud Infrastructure: Insights and Solutions(yugabyte.com)
2 points by gwen-shapira 3y ago|0 comments
38.
by gwen-shapira 3y ago
PG 11 is end-of-life, right? So you won't be getting new security updates. What's worse, libraries will stop supporting it over time, so you'll find it difficult to stay up to date in other places in your stack. If I was run
39.
by gwen-shapira 4y ago
When I first became a product manager, my director, the amazing Chrix, taught me about Lead Bullets. It proved true and useful again and again. When you sell to engineers, there are no alternatives to a good product. You can't BS your
40.
Did Postgres Lose My Data?(ardentperf.com)
2 points by gwen-shapira 4y ago|0 comments
41.
by gwen-shapira 4y ago
I just shared an interesting fact that I learned while posting on Substack this morning. I don't know the reason, and generally I don't think of product changes in terms of good and evil.
42.
Is Scalable OLTP in the Cloud a Solved Problem? (CIDR 23) [pdf](cidrdb.org)
2 points by gwen-shapira 4y ago|0 comments
43.
by gwen-shapira 4y ago
Substack also removed the "Also publish to Twitter" checkbox from the settings screen before publishing each post.
44.
SQL: 2023 is finished: Here is what’s new(peter.eisentraut.org)
4 points by gwen-shapira 4y ago|0 comments
45.
The Insatiable Postgres Replication Slot(morling.dev)
4 points by gwen-shapira 4y ago|1 comments
46.
by gwen-shapira 4y ago
This troubleshooting story explores an apparently common gotcha with PG's WAL replication. The details shared are useful to those who rely on PG's WAL replication.
47.
by gwen-shapira 4y ago
Thanks for sharing the product insight that drove your new version. I am seeing the same issue in the data space, even non-regulated companies store all their data in their account and in data stores that they control.
48.
by gwen-shapira 4y ago
Thanks for the feedback. I generally agree with you - there are too many systems that start off as quick productivity and then you get stuck. So there has to be options and composability in a platform. I really agree that you need to have a
49.
Things Databases don't do – but should(thenile.dev)
16 points by gwen-shapira 4y ago|3 comments
50.
Compute-Storage Separation – Explained(thenile.dev)
1 points by gwen-shapira 4y ago|0 comments
51.
by gwen-shapira 4y ago
Whether FTX US is solvent: “We still have a hole in the U.S., so as we sit here today it is not solvent. That's just inaccurate. And I'm not sure how he would even know that, quite honestly.” This is a good point. Hard to claim th
52.
Launching an Infrastructure SaaS Product, an Example Walkthrough(thenile.dev)
10 points by gwen-shapira 4y ago|0 comments
53.
by gwen-shapira 4y ago
oops :) Too many tabs. Fixed and thank you.
54.
by gwen-shapira 4y ago
The blog explicitly said that if the requirements involve actual authorization models (beyond simple tenancy) then RLS is not the best fit (see: https://thenile.dev/blog/multi-tenant-rls#if-you-have-sophis... ). I think
55.
by gwen-shapira 4y ago
"Although Bell and Telus offered to help, Rogers quickly determined that it would not be able to transfer its customers to its rivals’ networks because certain elements of the Rogers network, such as its centralized user database, were
56.
Architecting and implementing infrastructure SaaS – the hard parts(docs.thenile.dev)
2 points by gwen-shapira 4y ago|0 comments
57.
by gwen-shapira 4y ago
Any plans to also support Pulumi?
58.
by gwen-shapira 4y ago
Managing untrusted clients seems extremely challenging. I think these days you'd use something more "sandboxed" like WASM as the basis for the client?