Group items tagged

Es un chiste no? :)

El título lo pregunta, no lo afirma. ¿por qué decis que la prueba está mal hecha?

Si, bueno, donde puse "dice" quise decir "pregunta". Se pregunta si apache 2.4 es mas rápido que nginx, como una cosa novedosa, ya que es sabido lo contrario para versiones anteriores de apache, y que los devs de apache salieron a decir que el 2.4 es mas rápido que nginx. La prueba parece floja por varios lados... en los comentarios se mencionan varias cuestiones. Paradójicamente lo que sí es creíble es la conclusión, independientemente de la prueba. Aunque contradice las declaraciones de los devs de apache.

A new "Least Time" load-balancing algorithm Full-featured TCP load balancing High availability and failover between NGINX Plus instances A new statistics dashboard and improved monitoring Support for SSL authentication of email traffic (IMAP, POP3, and SMTP)

Why a transition to microservices and cloud development is necessary and why monolithic architectures aren't an option anymore. How to implement Docker in a cloud and continuously integrated environment and what the typical Docker-run applications look like. How NGINX and NGINX Plus can help support your migration to the modern way of building, deploying, and scaling applications.

"A programmable Nginx container"

"Automated Nginx reverse proxy for docker containers"

Generador de configuraciones de conectores ssl de apache, nginx, haproxy optimizadas por versión del servidor, antiguedad de clientes a soportar, etc. Muy bueno.

"The new Docker Registry 2.0 was released on April 16th, 2015. It was completely rewritten in Go with added support for the new Docker Registry HTTP API V2 (thus only working with Docker 1.6+), promising to provide faster and more secure distribution of images. If you work with Docker and for some reason decided not to use the public Docker Hub, a private Docker Registry is an essential part of your architecture. But even if you don't have private images, you will likely need to use your own registry in production/testing for efficiency. The default installation, however, runs without encryption and authentication. I was wondering what's involved in securing it. There is an official tutorial on how to configure TLS on a registry server. TLS/SSL is absolutely necessary for any secure setup, but I also wanted to enable an authentication mechanism. The Configuration Reference document describes two authentication options supported by Docker Registry itself: so-called silly and token solutions. The silly one is apparently only useful for very limited development use-cases. The token solution seems to be more serious, but because of the lack of documentation (at the time of writing), I decided to find an alternative approach to secure it. In this article I'm going to show you how to set up the Docker Registry 2.0 with username/password authentication and SSL using the official Docker Registry image and a custom configured nginx as a proxy server."

"Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and "universal data plane" designed for large microservice "service mesh" architectures. Built on the learnings of solutions such as NGINX, HAProxy, hardware load balancers, and cloud load balancers, Envoy runs alongside every application and abstracts the network by providing common features in a platform-agnostic manner. When all service traffic in an infrastructure flows via an Envoy mesh, it becomes easy to visualize problem areas via consistent observability, tune overall performance, and add substrate features in a single place."

"Secure, Manage & Extend your APIs and Microservices The open-source management layer for APIs, delivering high performance and reliability."

Benchmarks serios y abundantes de servidores HTTP y muchos números muy sorprendentes...