"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."
"Docker Inc. express a preference that container labels should be namespaced. Label Schema is a community project to provide a shared namespace for use by multiple tools, specifically org.label-schema.
By providing a shared and community owned namespace we aim to:
Avoid duplication in cases where the same information is needed in multiple labels
Encourage the use of labels, both by image creators and by tool builders which might consume them
Codify good community practice in a way that is easy to consume and keep up-to-date with"
"There’s a lot of outdated information on the Web that leads new PHP users astray, propagating bad practices and insecure code. PHP: The Right Way is an easy-to-read, quick reference for PHP popular coding standards, links to authoritative tutorials around the Web and what the contributors consider to be best practices at the present time.
There is no canonical way to use PHP. This website aims to introduce new PHP developers to some topics which they may not discover until it is too late, and aims to give seasoned pros some fresh ideas on those topics they’ve been doing for years without ever reconsidering. This website will also not tell you which tools to use, but instead offer suggestions for multiple options, when possible explaining the differences in approach and use-case.
This is a living document and will continue to be updated with more helpful information and examples as they become available."
MySQL application developers have some problems with connection state. There is a lot of state which can be used associated with a single connection
* Transactions (autocommit, uncommitted work, when a transaction was started, isolation level)
* Temporary tables
* Session variables which affect behaviour
* Other session variablesIf you can avoid all of these, then you can benefit from transparent auto-reconnection and transparent connection reuse / pooling etc.