Tried running it on the cloud dev environments I usually use (as I am on Windows myself).
Gitpod:
2023-03-29 18:13:54.044 UTC: [alloydb_util.sh:90] FATAL: Docker service must be active to run AlloyDB Omni
GitHub Codespaces (after increasing memory):
2023-03-29 18:37:55.236 UTC: [alloydb_util.sh:76] FATAL: AlloyDB Omni requires cgroups V2 to run.
GitHub Actions:
2023-03-29 18:53:52.766 UTC: [alloydb_util.sh:44] AlloyDB requires at least 16GB of RAM to run. Only 7 GB available. Please increase available RAM and retry
Not today it seems. Shame, sounded super interesting.
Yeah, I know. Apologies. Stay tuned though! For the tech preview launch we really focused on a golden path (narrow). We'll be expanding compatibility as we march towards GA.
The article ends with the statement that you are pretty much done here for now. Would optimizing your TLS termination not maybe offer some more ways to speed this up? Or is that also already fully optimized?
I did not realize before that your approach with Websockets actually meant that there was no application/client side pooling of connections. What made you choose this approach over an HTTP API (as for example PlanetScale did) anyway?
> The article ends with the statement that you are pretty much done here for now. Would optimizing your TLS termination not maybe offer some more ways to speed this up? Or is that also already fully optimized?
No, we don't do early termination yet, but it makes sense to try it out too. Here we mostly concentrated on how far we can get in terms of reducing number of round-trips.
> I did not realize before that your approach with Websockets actually meant that there was no application/client side pooling of connections. What made you choose this approach over an HTTP API (as for example PlanetScale did) anyway?
To keep compatibility with current code using postgres.js.
The general developer community and their deployments, most of that traffic are binaries (<20MB) that are part of a database client that are downloaded on installation of our Client libraries. So a _lot_ of CI traffic, but also the development machines which follow roughly the general developer distribution around the world (and includes pretty much any country you can think of as far as we know).
Sometimes S3+Cloudfront is a bit faster, sometimes Cloudflare, and sometimes either of them are _really_ slower than the other one as well. I don't see any pattern yet, both in comparing the two but also for which locations are affected and so on.
Which might mean it would be roughly the same on average - but I was hoping someone else could help me go beyond this napkin math by sharing there practical experiences.
> [...] followed by instructions on how to download and install the update, which Microsoft said has been scanned to ensure it's not infected by malware.
>
> "Microsoft scanned this file for viruses by using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it," the Windows giant said on the update notice page.
Prisma has pivoted to be “just” a Node.JS ORM a few years ago (I work there). You can still use it to build an API of course, but you will need some additional tool or libraries.
Why did Prisma pivot to this? It sounded to me that offering a ready-to-go GraphQL API ala Firebase was a great idea and could certainly turn good profits.
We observed that people migrated off as soon as the applications went into production or were serious, as the database<->api approach did not actually give them all the flexibility they wanted.
(This was 3 years ago, the players that stayed in that market or entered later, of course learned from that and adapted. So I hear they are making their users happy. As are we as an ORM.)
slightly more perverse, if you're interested in the space... I happen to know this guy from high school and the stories behind his performances are fascinating
Gitpod:
GitHub Codespaces (after increasing memory): GitHub Actions: Not today it seems. Shame, sounded super interesting.