David Ellis
David Ellis
Will note that option 1 requires us to expose the RDS URL to end users, instead of using our own domain name for this.
> The parent of the child process is the Express.js server, so if we kill the parent on error the whole container will be restarted. Is that ok? So respawning...
> Regarding the use of JSON-RPC, there are some considerations: > > You had mentioned `multitransport-jsonrpc` in the source code, but I think you're not actively maintaining it at the...
> Have looked into https://nodejs.org/api/cluster.html or considered it? If so, curious why we ruled it out Well, we only have one child and all of the same things we need...
Hi @AshnaSabu123 So that's actually expected. The visual dashboard is part of our SaaS offering and is not in this repository. When you run locally it's just two commands to...
No longer needed after the discovery used in #238
Oh, wait, this is the wrong issue.
Digging into this task: 1. Aurora is treated by the SDK as just another feature of RDS (though with wildly non-overlapping configuration knobs). Whether we should break this out into...
So, Amazon has Aurora inside of RDS in the dashboard as a special database type with two configurations. It also automatically requires you to name the "DB cluster" instead of...
Why `Aurora` is not given top-level billing while `Dynamo` is makes no sense to me. AWS's marketing is totally inconsistent, just like their APIs, but we wanted to keep our...