The default formula use by AWS RDS to calculate the max_connections parameter is: LEAST({DBInstanceClassMemory/9531392},5000)
But It's hard to find the exact value of DBInstanceClassMemory.
So, here are the values I got when I ran the SQL commmand: show max_connections; in some RDS instances:
| Instance type | RAM (GB) | max_connections |
|---|---|---|
| db.t2.small | 2 | 198 |
| db.t2.medium | 4 | 413 |
| package main | |
| import ( | |
| "context" | |
| "flag" | |
| "fmt" | |
| "log" | |
| "net/http" | |
| "os" | |
| "os/signal" |
| #!/bin/sh | |
| command="${*}" | |
| printf "Initialized REPL for `%s`\n" "$command" | |
| printf "%s> " "$command" | |
| read -r input | |
| while [ "$input" != "" ]; | |
| do | |
| eval "$command $input" | |
| printf "%s> " "$command" |
| @echo off | |
| setlocal EnableDelayedExpansion | |
| ver | find "10." > nul | |
| if errorlevel 1 ( | |
| echo Your Windows version is not Windows 10... yet. Brace yourself, Windows 10 is coming^^! | |
| pause | |
| exit | |
| ) |
| { | |
| "AWSEBDockerrunVersion": "1", | |
| "Image": { | |
| "Name": "<AWS_ACCOUNT_ID>.dkr.ecr.us-east-1.amazonaws.com/<NAME>:<TAG>", | |
| "Update": "true" | |
| }, | |
| "Ports": [ | |
| { | |
| "ContainerPort": "443" | |
| } |
Currently, there is an explosion of tools that aim to manage secrets for automated, cloud native infrastructure management. Daniel Somerfield did some work classifying the various approaches, but (as far as I know) no one has made a recent effort to summarize the various tools.
This is an attempt to give a quick overview of what can be found out there. The list is alphabetical. There will be tools that are missing, and some of the facts might be wrong--I welcome your corrections. For the purpose, I can be reached via @maxvt on Twitter, or just leave me a comment here.
There is a companion feature matrix of various tools. Comments are welcome in the same manner.
A curated list of "What are the best..." questions related to development.
All the questions are taken from here
Quality Assurance
| # <type>: (If applied, this commit will...) <subject> (Max 50 char) | |
| # |<---- Using a Maximum Of 50 Characters ---->| | |
| # Explain why this change is being made | |
| # |<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->| | |
| # Provide links or keys to any relevant tickets, articles or other resources | |
| # Example: Github issue #23 |
We will compare ASP.NET and Node.js for backend programming.
Source codes from examples.
This document was published on 21.09.2015 for a freelance employer. Some changes since then (14.02.2016):
async/await. yield and await are used almost in the same way, so I see no point to rewrite the examples.
A running example of the code from:
This gist creates a working example from blog post, and a alternate example using simple worker pool.
TLDR: if you want simple and controlled concurrency use a worker pool.