State of the art security for the most valuable secrets. We will cover the “perfect” way to handle password credentials from the moment a user types them into a form on the client-side, till the moment they are stored in the database. Furthermore, we will look into common errors, that happen when developers store other credentials like Tokens/Secrets/etc.
Each pattern describes the problem that the pattern addresses, considerations for applying the pattern, and an example based on Microsoft Azure. However, most of the patterns are relevant to any distributed system, whether hosted on Azure or on other cloud platforms.
Using ServerLess in AWS you have to pay for the API Gateway. The gateway alon at high request rate cost $12k/month. Rewritten in Elixir and it’s free since they are running on leftover compute of Kubernetes.
Want some fun? Let’s implement a chess engine :). The author claims he has trouble beating it
Another post in this serie from SessionStack. In this we forcus on best practices for building reusable components.
Setup an iOS project environmentSwift
A simple TUN/TAP library written in native GoGo
Set up a personal IPSEC VPN in the cloudAnsibleDevOps
Gather metadata about your S3 bucketsRust
embedded trie key-value databaseC
Robust, modular, and extendable user authentication systemElixir
Interactive ReasonML sketchbookReasonMLOcaml
a static analysis tool for shell scripts
Human readable time diffs on lines of output when running
The first language for Microservices
command-line utility for creating and maintaining your own set of man-like help pages
GitHub Flow for Kubernetes
Better Dev Link