4 ms·

That pricing is quite "less generous" than Turso: https://turso.tech/pricing https://turso.tech/pricing I'm wondering what accounts for the difference; is Turs

That pricing is quite "less generous" than Turso: https://turso.tech/pricing https://turso.tech/pricing I'm wondering what accounts for the difference; is Turso just bleeding money on smaller tiers, etc?

johtso 3y ago
Turso is sqlite not postgresql
- yawnxyz 3y ago
  as a "mere user" of the JS or API endpoints, should I think one is better than the other? To me it doesn't really matter if it's Supabase/Neon, Turso, or D1 powering it as long as... it works Is this faster / more resilient?
  - djha-skin 3y ago
    I'd probably care because of the ecosystem. There's a bunch of developer tooling and mature ORMs around postgres. Granted, those same libraries/frameworks probably work with sqlite too. I guess it's just trust. I trust postgres more than I trust sqlite for building big apps. One last point: I'd look at feature set of both offerings. I suspect the features of the postgres offering to be more conducive to scale.
  - nop_slide 3y ago
    They both could be faster or more resilient depending on your workload and what you want that to mean. Take some time to learn about the differences between postgres and sqlite it is good to know about the trade offs.
  - filleokus 3y ago
    With Turso you get an sqlite database behind a SDK or an (HTTP REST) API endpoint. With Neon you get a postgresql database over a postgres wire format connection. So if you have an already existing app speaking postgres to a database somewhere, Neon is a drop-in-replacement, while Turso would require adapting to their custom API. If you are creating a new service, you might need/want to take advantage of e.g postgres extensions [0] for storing geographical data or pg_vector for similarity searches etc. Or you simply need more stringent serialisability promises than what libsql / turso can provide. But if you just writing something new from scratch and have "simple" demands, I think something like Turso looks cool (and cheap!). [0]: https://neon.tech/docs/extensions/pg-extensions https://neon.tech/docs/extensions/pg-extensions
SwiftyBug 3y ago
The founder of Turso explained how they can have such a generous free tier in a tweet: > Lots of people have been reaching out to me asking if they should expect our free tier to be around, given recent news. > Yes, you can expect our free tier to be around. > The main reason we built a service on SQLite is that we knew we could build the most efficient thing in the market with that. I usually keep these number semi private, but last month Turso had over 20,000 databases under management - in all plans - and our Cloud bill was less then 3.5K USD. > I sympathize with Planetscale, in the sense that running a company is hard and you sometimes have to make hard choices. But look beyond words, into cost structures and incentives: > Of course our service is expensive to operate, like any service, but most of it is staffing. We'll never find ourselves in a situation where killing our free tier will make any dent in the profitability of the company. https://twitter.com/glcst/status/1765466864338034717 https://twitter.com/glcst/status/1765466864338034717

johtso 3y ago

Turso is sqlite not postgresql

yawnxyz 3y ago
as a "mere user" of the JS or API endpoints, should I think one is better than the other? To me it doesn't really matter if it's Supabase/Neon, Turso, or D1 powering it as long as... it works Is this faster / more resilient?
- djha-skin 3y ago
  I'd probably care because of the ecosystem. There's a bunch of developer tooling and mature ORMs around postgres. Granted, those same libraries/frameworks probably work with sqlite too. I guess it's just trust. I trust postgres more than I trust sqlite for building big apps. One last point: I'd look at feature set of both offerings. I suspect the features of the postgres offering to be more conducive to scale.
- nop_slide 3y ago
  They both could be faster or more resilient depending on your workload and what you want that to mean. Take some time to learn about the differences between postgres and sqlite it is good to know about the trade offs.
- filleokus 3y ago
  With Turso you get an sqlite database behind a SDK or an (HTTP REST) API endpoint. With Neon you get a postgresql database over a postgres wire format connection. So if you have an already existing app speaking postgres to a database somewhere, Neon is a drop-in-replacement, while Turso would require adapting to their custom API. If you are creating a new service, you might need/want to take advantage of e.g postgres extensions [0] for storing geographical data or pg_vector for similarity searches etc. Or you simply need more stringent serialisability promises than what libsql / turso can provide. But if you just writing something new from scratch and have "simple" demands, I think something like Turso looks cool (and cheap!). [0]: https://neon.tech/docs/extensions/pg-extensions https://neon.tech/docs/extensions/pg-extensions

SwiftyBug 3y ago

The founder of Turso explained how they can have such a generous free tier in a tweet: > Lots of people have been reaching out to me asking if they should expect our free tier to be around, given recent news. > Yes, you can expect our free tier to be around. > The main reason we built a service on SQLite is that we knew we could build the most efficient thing in the market with that. I usually keep these number semi private, but last month Turso had over 20,000 databases under management - in all plans - and our Cloud bill was less then 3.5K USD. > I sympathize with Planetscale, in the sense that running a company is hard and you sometimes have to make hard choices. But look beyond words, into cost structures and incentives: > Of course our service is expensive to operate, like any service, but most of it is staffing. We'll never find ourselves in a situation where killing our free tier will make any dent in the profitability of the company. https://twitter.com/glcst/status/1765466864338034717 https://twitter.com/glcst/status/1765466864338034717