Every container you run with Docker, Podman, Cri-o or Containerd is, down the stack, launched with runc.

#container

#container ecosystem

The Free #Software Foundation defines it as “the users
have the freedom to run, copy, distribute, study, change and improve the software. Thus, free
software is a matter of liberty, not price.” Historically, the free software community has
used the analogy of “free” as in “free speech,” not “free” as in “free beer."

ZERO TRUST-AI.pdf
#security #ai

A security framework for deploying autonomous Al agents in the enterprise.

#cloud #k8s

#docker commands cheat sheet

10 #microservices #design patterns for better #architecture

1. #Database per #service pattern

The database is one of the most important components of microservices architecture, but it isn’t uncommon for developers to overlook the database per service pattern when building their services. Database organization will affect the efficiency and complexity of the application. The most common options that a developer can use when determining the organizational architecture of an application are:
Dedicated database for each service:

A database dedicated to one service can’t be accessed by other services. This is one of the reasons that makes it much easier to scale and understand from a whole end-to-end #business aspect.

2. Saga #pattern
A saga is a series of local transactions. In #microservices #applications, a saga pattern can help maintain #data consistency during distributed transactions.

#NetOps for networks, #DataSecOps for data engineering, #MLOps for machine learning, #NoOps for operations, and #EdgeOps for edge computing

3. API gateway pattern
For large applications with multiple clients, implementing an #API gateway #pattern is a compelling option One of the largest benefits is that it insulates the client from needing to know how services have been partitioned.

4. Aggregator design pattern

An aggregator design #pattern is used to collect pieces of #data from various microservices and returns an aggregate for processing. Although similar to the backend-for-frontend (BFF) design pattern, an aggregator is more generic and not explicitly used for UI.