FAUN

I would second the opinion that the techniques demonstrated here are several years behind current best practices. Automation is the right course, but this takes a very roundabout way toward producing an artifact that can be distributed and applied repeatably, compared to using something like an Ansible playbook that is applied using Virtualbox's built-in Ansible provisioner. I would recommend anyone reading this thread against recreating this, except as a proof of concept, and instead concentrate on a workflow more similar to this one: https://medium.com/faun/building-repeatable-infrastructure-with-terraf…

This is great news! We at VictoriaMetrics [1] are happy that TimescaleDB eventually addressed high disk usage issue and implemented type-aware column-based compression. This should improve its' position and performance in TSBS benchmark [2]. One question: why do you use Gorilla compression for floating-point values? It works well for integer values, but is pretty useless for floating-point values [3]. [1] https://github.com/VictoriaMetrics/VictoriaMetrics [2] https://medium.com/@valyala/measuring-vertical-scalability-for-time-se… [3] https://medium.com/faun/victoriametrics-achieving-better-compression-f…

This article seems to be copied word for word from this article from February with a few other things added. https://medium.com/faun/10-useful-kubernetes-tools-ddffa62089cc

This may be interesting for you - a vault terraform provider using envelope encryption To get secrets from terraform into vault https://medium.com/faun/provisioning-vault-encrypted-secrets-using-ter…

You can simply dockerize your app and deploy it to Heroku: https://medium.com/faun/how-to-dockerize-a-net-core-application-and-de…

Lambda may not be a magic reliability wand, you definitely still need to manage downstream pressure. That said: > The code creates a MySQL connection during each invocation. This is not a correct implementation for Lambda. You shouldn't recreate a connection on every invocation. Instead, create your connection outside of your handler code. Then each invocation of a warm container will re-use the same handler. (1) This will help cut down on cold start time, as well as help manage running out of connections. You should limit your maximum number of concurrent invocations to be equal to the limit of your database threadpool. This is all in their documentation, as well as several blog posts. (2, 3, 4) [1] https://docs.aws.amazon.com/lambda/latest/dg/services-rds-tutorial.htm… [2] https://www.jeremydaly.com/reuse-database-connections-aws-lambda/ [3] https://medium.com/faun/reusing-connections-lambda-functions-poc-1eb80…

Here are some resources I collected over the time References: https://chrisshort.net/kubernetes-illustrated-childrens-guide https://docs.google.com/spreadsheets/d/10NltoF_6y3mBwUzQ4bcQLQfCE1BWSg… (The Kubernetes Learning Resources List) https://github.com/jamiehannaford/what-happens-when-k8s https://github.com/kubernetes/kubernetes https://github.com/nkuba/k8s-admin-helper https://github.com/ramitsurana/awesome-kubernetes https://github.com/topics/cka?o=desc&s=stars https://github.com/topics/kubernetes?o=desc&s=stars https://k3s.io https://kind.sigs.k8s.io https://kubernauts-slack-join.herokuapp.com https://kubernetes.io/docs/concepts https://kubernetes.io/docs/reference/kubectl/cheatsheet https://kubernetes.io/docs/tasks https://kubernetes.io/docs/tasks/manage-kubernetes-objects/imperative-… https://kubernetes.io/training https://kubernetesbyexample.com https://labs.play-with-k8s.com https://medium.com/faun/be-fast-with-kubectl-1-18-ckad-cka-31be00acc44… https://news.ycombinator.com/item?id=22597880 (Kind - run local Kubernetes clusters using Docker (k8s.io)) https://news.ycombinator.com/item?id=22689119 (Anyone have a recommended guide for Kubernetes?) https://rancher.com https://slack.k8s.io https://techbeacon.com/enterprise-it/47-advanced-tutorials-mastering-k… https://www.facebook.com/groups/kubernetes.users https://www.facebook.com/kubernetesio https://youtu.be/0Omvgd7Hg1I (Life of a Packet [I] - Michael Rubin,…

http://highscalability.com/ https://medium.com/faun

Here is my non complete list: - Who’s at the Helm? [0] - Microservices, hard as 1, 2, 3 - You can move it but complexity is still here [1] - Microservices — architecture nihilism in minimalism's clothes [2] - Do I Really Need Kubernetes? [3] - Your team might not need Kubernetes [4] I doubt that any of those articles could convince higher management. I don't know what a "respected source" actually means. I general I believe that advice from consulting agency and cloud providers should be taken with a grain of salt. If you drew the same conclusion from the "Who’s at the Helm?" article than I, there is only one way out which is a curated container catalog. VMware's Tanzu Application Catalog [5] is the only product in that space I'm aware of. I have quoted the price tag on HN, I think it was removed since that, so I won't repeat it here again. In any way it was magnitudes higher than the EKS base price which already seen as a showstopper by many small shops. Bottom line is: it is really hard and really expensive to operate containers in a secure manner. Probably too hard and too expensive that it would be a good idea to start with it before you actually need it. 0: https://dlorenc.medium.com/whos-at-the-helm-1101c37bf0f1 1: https://medium.com/@danielpetisme/microservices-hard-as-1-2-3-af4e3389… 2: https://vlfig.me/posts/microservices 3: https://thenewstack.io/do-i-really-need-kubernetes/ 4: https://medium.com/faun/your-team-might-not-need-kubernetes-57240e8d55… 5:…