Live data from Hacker News

Astro DB

astro.build

11–20 of 43 posts

Re: Astro DB

#11
I dig Astro and use it to build my blog and several other tiny mostly-static sites. I'm not sure that the hosted database service fills a need I have but, in general, supported SQL integration seems like a useful addition.

As an aside: there are days when I wish I could avoid using the Astro component model entirely, do everything in Preact (or whatever), and still use the `client:*` directives when appropriate. I realize this is easier said than done and also probably not a reasonable thing for Astro itself to try and target -- but moving between Astro components and framework components always has just enough friction that it's something I think I'd enjoy using.

Re: Astro DB

#12

I dig Astro and use it to build my blog and several other tiny mostly-static sites. I'm not sure that the hosted database service fills a need I have but, in general, supported SQL integration seems like a useful addition. As an aside: there are days when I wish I could avoid using the Astro component model entirely, do everything in Preact (or whatever), and still use the `client:*` directives when appropriate. I re…

This is probably the main reason I wouldn’t choose Astro for personal projects where it’s otherwise a great fit. I think it would have been a more reasonable thing earlier on in product conception, but quite a lot of assumptions are now baked into their own custom template language. Which I’m sure is quite a nice template language, but it’s already hard enough to get all the tools to work nicely together without adding another one.

Re: Astro DB

#13

I'm currently thinking about using either Astro or SvelteKit for my next project. Astro DB suggests that Astro aims to be more than just a static site builder. However, all over the internet, I read that Astro is primarily a static site builder, and if I want to build a fully-featured web application, I should use something like Next.js or SvelteKit. Now, I'm a little bit confused where Astro DB fits into this pictur…

It used to be a nice site builder, for static sites and apps, but has grown into another full-featured framework of sorts. And is now sliding into SaaS.

Re: Astro DB

#15
Slightly tangential -- anyone knows how does libSQL compare to upstream SQLite for shipping with a desktop app or in the browser via wasm?

Edit: I've read the readme, hoping for a take from anyone who gave it a try

Re: Astro DB

#16
The ORM API is very reminiscent of Drizzle, which I think was a great call on Astro's side. I have so far only used Astro for SSG, but seeing code like this [1] has me interested to see how far it can go for SSR tasks that you might currently use metaframeworks such as Next/Nuxt/SolidStart/SvelteKit for.

[1] https://docs.astro.build/en/guides/astro-db/#insert

Re: Astro DB

#17

I dig Astro and use it to build my blog and several other tiny mostly-static sites. I'm not sure that the hosted database service fills a need I have but, in general, supported SQL integration seems like a useful addition. As an aside: there are days when I wish I could avoid using the Astro component model entirely, do everything in Preact (or whatever), and still use the `client:*` directives when appropriate. I re…

This is probably the main reason I wouldn’t choose Astro for personal projects where it’s otherwise a great fit. I think it would have been a more reasonable thing earlier on in product conception, but quite a lot of assumptions are now baked into their own custom template language. Which I’m sure is quite a nice template language, but it’s already hard enough to get all the tools to work nicely together without addi…

Yeah, I started poking at Vite to see how much work it would take to build an island-architecture-for-preact tool on top of it. It looks doable.

Out of curiosity, when you're building a mostly static site that might want occasional islands of interactivity, what do you reach for instead?

Re: Astro DB

#18
post #2

So what's the added value over Turso + Drizzle?

It seems to be wrapping drizzle, with astrodb just being a way to deeper integrate it into the framework and adding some ease of use features. Also seems like a nice way to support the development of astro by using their hosting service.

So it is the wrapper for wrapper (Drizzle) for Kysely?

Re: Astro DB

#20
What do they do to mitigate the roundtrip latency introduced by using a hosted database on a separate network? Is the idea that you wouldn't use this if you have pages that do many queries to render?
Post reply on HN