"How is software developed at Amazon? Get a couple of prime pizzas delivered and watch this excellent interview with Ken Exner, GM of AWS Developer Tools. It's notable Ken is from the tools group, because progress in an industry is almost always made possible by the development of better tools.
The key themes from the talk: decomposition, automation, and organize around the customer."
"In this practical eBook, the author Russ Miles explains how Observability and Chaos Engineering go hand-in hand, since the fundamental process of running chaos experiments is built around the live observability of the engineered chaos testing. The eBook will will help you learn how to test and observe the health and resiliency of your systems and security controls, in real-time, by bringing observability to chaos engineering.
"
"Services should own both reads and writes to their own data. If several services need access to the same data, this is done via the owning service's API. Services should address a specific concern. For Airbnb, this was about trying to find the right granularity when creating services. They wished to avoid services having too much functionality, becoming monoliths in their own right, while also avoiding such fine-grained services that there would be a "polylith" or distributed monolith. Avoid duplicate functionality by using shared services and libraries. Data mutations should publish via standard events."
"Notable changes since we last reviewed this topic include "microservices" moving into the late majority, but our internal discussions also highlighted that the closely related themes of "correctly designing distributed systems", and designing for reactivity and fault tolerance are not so far along the adoption curve. We may well be approaching the bottom of the microservice “trough of disillusionment” in respect to the Gartner Hype Cycle.
We have also speculated that there are areas of architecture that will never move along the adoption curve to early majority or late majority, and unfortunately, they include several highly-effective patterns -- such as event-sourcing/CQRS-based or Actor model-based systems -- which can provide highly effective solutions for certain organisations and business problems."
"In July 2018, leaders of the O'Reilly Software Architecture Conference conducted a survey on microservices maturity to assess just how far organizations have come with this technology, including the practices they follow and the challenges they face along the way.
The responses we received are summarized in this report."
" This notes describes how to improve Nginx performance, security and other important things; ssllabs A+ 100%. "
"In this post I will show you how to use Roles published to Ansible Galaxy as an Operator to manage an application in Kubernetes. Reusing a Role in this way provides an example of how to create an Operator that simply installs an application with the flexibility to expand and customize the behavior organically as requirements dictate.
I will leverage both the Ansible Operator and the k8s module to demonstrate how you can use Ansible to create Kubernetes native applications. Ansible Operator, included in the Operator SDK, allows you to package your operational knowledge (how you install and maintain your application) in the form of Ansible Roles and Playbooks. Your ability to manage objects in Kubernetes when writing these Roles and Playbooks can be improved by the new k8s module."
"Realtime license and vulnerability management for open source dependencies "
" Kubernetes is a fairly complex system with many moving parts. Its ecosystem is constantly evolving and adding even more layers (service mesh, ..) to the mix. Considering this environment, we don't hear enough real-world horror stories to learn from each other! This compilation of failure stories should make it easier for people dealing with Kubernetes operations (SRE, ops, platform/infrastructure teams) to learn from others and reduce the unknown unknowns of running Kubernetes in production."
Atlantis is an application for automating Terraform via pull requests. It is deployed as a standalone application into your infrastructure. No third-party has access to your credentials.
Atlantis listens for GitHub, GitLab or Bitbucket webhooks about Terraform pull requests. It then runs terraform plan and comments with the output back on the pull request.
When you want to apply, comment atlantis apply on the pull request and Atlantis will run terraform apply and comment back with the output.
"1-click deployment of OpenVPN with DNS ad blocking sinkhole. Deploys to your favorite VPS machine. Created with Vue.js, Semantic UI and Django. And with love, of course.
"
1: Always run at least 2 pods 2: Spread your application pods evenly across nodes 3: Define a pod disruption budget 4: Define a descheduler policy 5: Do not use local/host path storage 6: Design your application so that it tolerate losing pods 7: It shouldn’t matter which pod receives a request 8: Capacity considerations
"krew is a tool that makes it easy to use kubectl plugins. krew helps you discover plugins, install and manage them on your machine. It is similar to tools like apt, dnf or brew.
For kubectl users: krew helps you find, install and manage kubectl plugins in a consistent way. For plugin developers: krew helps you package and distribute your plugins on multiple platforms and makes them discoverable."
"Operators are Kubernetes native applications. We define native as being both managed using the Kubernetes APIs via kubectl and ran on Kubernetes as containers. Operators take advantage of Kubernetes’s extensibility to deliver the automation advantages of cloud services like provisioning, scaling, and backup/restore while being able to run anywhere that Kubernetes can run.
This list is built by the community. Have you built or are you using an Operator that is not listed? Please send a pull request and we will add that Operator to the list."
"Go binary to change Docker container user/group and file permissions at runtime "
