I started with RFC 1034 and 1035 to understand the protocol specs and header bit-masks. For the practical side, I used Cloudflare’s DNS docs to understand the recursive logic.
For coding, I relied on Go's dnsmessage documentation. I also used Gemini to help me with codes.
> A tool for creating and running Linux containers using lightweight virtual machines on a Mac. It is written in Swift, and optimized for Apple silicon.
I may be missing the point of this, other than maybe being able to bypassing some network filtering. At first I was excited, thinking perhaps it's browser based and that it somehow bypassed CORS. But upon further inspection, it's piping everything through their domain. I have no idea whether or not they're trustworthy. I would not be submitting any credentials with this.
I browsed the documentation and saw no references to provisioning database compute/memory resources. Is the persistence serverless, autoscaling, and scale to zero?
Yes but it says nothing about cpu/ram and/or memory/storage/io optimized hardware, cost per hour, or anything like that. Does it scale to zero? Does it autoscale? Will it throttle with spikes in load?
Thanks for the good question! Our free tier offers fixed resources per application (under the hood, a Firecracker microVM with 512 MB of RAM and 1 vCPU) that scale to zero when not in use. For paid users, we'll offer autoscaling per application--we'll share more details on that soon.
reply