I can see that. Pydantic is great but relatively slow (which matters on edge devices) and can be bloated.
The fact that all your projects use Pydantic makes it an easy starting point and created standardisation - of course.
Nevertheless, I can definitely see some use-cases for lightweight JSON-serialisation without bringing in Pydantic. Dataclasses are great, but lack proper json handling.
I wonder if this isn't toooo much magic. How does this scale beyond simple use-cases? I fear one might hit a wall at 80%, where the first part is super easy indeed but not customizable enough to get to 100% of all use-cases.
Thanks! It's a great point to make. Early on I worked on a "migration" ability for the resources, so that every change you make automatically updates the underlying database. But the longer I worked on that, the more I realized I could create/delete as many APIs as I wanted working out what's necessary. Then scale it up for longevity. And the time it took to create/delete APIs was nearly as fast as some of the build times I've experienced for front-end applications.
That's ultimately what I think the value is: API development as hyper-iterative as front-end apps.
I'm still clearly working out how to describe this value. I'm developing more examples to help define what I think the best use-cases are.
Overall love the DX with Claude Code in my vscode (kinda hate all the CLI only approaches the rest have), but would be great to still utilize other models.
The speed mostly comes from building it on top of Starlette and Granian, while keeping overhead low, so I can't claim much credit on that part. In the end, business logic will be the bottleneck anyway :)
Yeah, I've seen mixed responses on SQL magic. Spring and Ruby devs I talked to seemed to like it (with Ruby active records having a similar feature), but JS, Python and other devs I talked to found it odd.
I guess it depends on the ecosystem people get used to?
Would be exciting to see Astral come out with a server! Though, with the current landscape, it feels like there isn't too much to be done without massive efforts, so I don't imagine they could justify spending the time given how well they're doing in their niche. Could be wrong, though.
Bedrock has strong contractual guarantees, but it's still only a legal contract and runs on AWS infra. This is certainly okay for many use cases, we're trying to build for users who want verifiable privacy guarantees beyond legal contracts.
We're also doing more than pure inference, and trying to work with other companies who want to provide their users additional verifiability and confidentiality guarantees by running their entire private data processing pipeline on our platform.
The fact that all your projects use Pydantic makes it an easy starting point and created standardisation - of course.
Nevertheless, I can definitely see some use-cases for lightweight JSON-serialisation without bringing in Pydantic. Dataclasses are great, but lack proper json handling.