"This repository provides resources for developers to keep their secrets secret.
"
"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."
" This notes describes how to improve Nginx performance, security and other important things; ssllabs A+ 100%. "
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
"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"
" Reproducible builds are a set of software development practices that create a verifiable path from human readable source code to the binary code used by computers. "
"Checklist of the most important security countermeasures when designing, testing, and releasing your API "
"If you create software that is planned for continuous enhancements and maintenance over several years then you'll need a sustainable strategy for code quality. Code coverage by automated tests is one important metric, and its value should equal 100% at all times. This talk will show why this is so and how it can be achieved in PHP / Symfony based applications."
"I love that illustrations have become such a key part of the tech branding landscape. But here's an observation: tech illustrations often feature the same sets of things: young, white people (usually men), surrounded by gadgets, with a cup of coffee, in a beautiful tech world.
For consumer-oriented products, this creates an incredibly limiting and exclusive brand image, unless you are solely targeting city-dwelling, coastal tech millennials."
"Since PHP 7.0, the OpCache extension is able to store the compiled OpCode into files.
This plugin add the warmup-opcode command to composer which triggers the compilation for every PHP file discovered in the project."
"This article aims to examine the benefits of Docker within the context of a software company with multiple developers working on multiple projects, having to manage these projects deployed in a cloud production environment. In this context the benefits of Docker become more readily apparent. "
"This is a collection of known design patterns and some sample code how to implement them in PHP. Every pattern has a small list of examples (most of them from Zend Framework, Symfony2 or Doctrine2 as I'm most familiar with this software).
I think the problem with patterns is that often people do know them but don't know when to apply which."
"Something I love with PHP is how easily you can build a CLI application. Some libraries like the Symfony Console Component has greatly improved this process. Also, the ability to package a whole application into a single PHAR container make the distribution and usage even easier.
"
