"Immersive terminal interface for managing docker containers and services
"
"Immersive terminal interface for managing docker containers and services
"
"A tool for exploring a docker image, layer contents, and discovering ways to shrink your Docker image size.
"
"This repository provides resources for developers to keep their secrets secret.
"
"A microservices-based application is split into small independent services that communicate with each other via APIs using lightweight protocols like HTTP, gRPC, Kafka and more. However, existing Linux network security mechanisms (e.g., iptables) only operate at the network and transport layers (i.e., IP addresses and ports) and lack visibility into the microservices layer.
Cilium brings API-aware network security filtering to Linux container frameworks like Docker and Kubernetes. Using a new Linux kernel technology called BPF, Cilium provides a simple and efficient way to define and enforce both network-layer and application-layer security policies based on container/pod identity."
"Easy to install. A binary of less than 40 MB. Only 512 MB of RAM required to run. "
"Encapsulated access to data storage with a single service as its owner Services should address a specific concern Avoid duplicate functionality Data mutations published via standard events Build with best practices for production, including technical architecture, observability, and alerts (avoid cutting corners for "prototypes", "only admins", or aggressive deadlines) Good practices include:
Standardization for consistent APIs, observability, client and server functionality, plus build and deploy processes Invest in tools and solutions to autogenerate code instead of relying on humans to manually write boilerplate and shared frameworks Include reliability and robustness features in autogenerated clients and servers; fail fast Perform comparisons of monolith and service request life cycles asynchronously to avoid adding extra latency to production paths Make RPCs to dependencies asynchronously to get performance benefits due to parallelization"
"Les systèmes sur lesquels nous travaillons évoluent dans le temps. Cette évolution s’applique également à leur architecture, la documentation de l’architecture se doit donc d’y être adaptée. C’est la problématique à laquelle se proposent de répondre les Architecture Decision Records, ou ADRs.
Cet article a pour objectifs de vous aider à comprendre ce qui définit un ADR et de vous donner quelques clés pour la mise en place de ce nouveau mode de documentation."
" Knative (pronounced kay-nay-tiv) extends Kubernetes to provide a set of middleware components that are essential to build modern, source-centric, and container-based applications that can run anywhere: on premises, in the cloud, or even in a third-party data center."
"ShellCheck is a GPLv3 tool that gives warnings and suggestions for bash/sh shell scripts:
"
"My simple Swiss Army knife for http/https troubleshooting and profiling. "
"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."