Astro DB
astro.build
Astro DB
1–10 of 43 posts
Re: Astro DB
#2So what's the added value over Turso + Drizzle?
Re: Astro DB
#3So 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.
Re: Astro DB
#4A lot of Astro news for the last 2 days:
- 4.5 release
- Volar $10,000 grant
- Astro Studio/DB
Re: Astro DB
#5Comments coming from a years-long Astro user that loves it. I use it to power my own website. I'm familiar with this space because I also work at Xata (take that as a disclosure).
This looks like a pretty simple data solution that might work for Astro's audience (content sites and hobbyists). They've split the hosting into their studio product to provide a way to earn revenue. Essentially you host the DB with them and can access it remotely, but could also host it however you want, you'd just lose the Studio editor.
The Studio editor itself is pretty basic at the moment with a table view and a way to check SQL calls. You can't build schemas in the UI yet and what you get is mostly a dev wrap of existing tools (like Drizzle) that let you interact with your DB. Their demo shows the limitations here, with things like "email" not being able to validate in the studio editor. My guess is that's coming later, but I might have missed it in the docs. Either way, it's nice that your config is stored at the code layer.
Most of these small websites that Astro is great fit need small CMS systems, and studio doesn't look to provide any way to deal with images (at least on first check) so that's sort of a bummer. You'd need to wire up some references with Cloudflare I guess. Still reading here, but it'd be cool if that came natively. Storing, retrieving and resizing images is a pain. The column types allowed are pretty small (text, number, bool, date, json).
While simple. It looks like it'll be relatively speedy with retrieval because of it.
Right now though, as an actual CMS editor (which my guess is what most Astro folks really want) Studio feels way to simple to tell a client to use. I'm interested to see whether they go more in the direction of a generic database store (implied from the name) or more of a CMS to compete with the natural pairings of Contentful, Statamic and others. Webhooks as a launch feature is great! That'll help folks out.
Either way. I love this team and their perspective. They build cool stuff, open source a lot of it (check out Starlight for docs), and I'm excited to see where this one goes over time. Congrats on the launch.
Now I need to update my Astro site to 4.5 :)
Re: Astro DB
#6Love that they use comments as an example. I miss this with many static blogs. HN comments are great, but I sometimes want to read a discussion between people who've actually read the article.
Re: Astro DB
#7Personally, I love Astro and use it personally (and at work). I hope this turns out as a great start to generating revenue.
Re: Astro DB
#8Interesting and even more compelling pricing, indeed a very generous free tier.
I only wish this wasn't a javascript heavy thing and that I could interface with it in my language of choice. But as it says on the tin this is integrated well for the greater Astro ecosystem.
Re: Astro DB
#9I get that all of the current generation of front-end/back-end frameworks promised their investors that they'd figure out how to sell developer services, rather than just offer open-source components with some extra commercial support options...
But I do wonder how this type of thing will actually compete against a billion headless CMSes and a million PaaSes already on the market...
Re: Astro DB
#10I'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 picture.