"This library provides a way to parse, scrape, and transform html5 pages using CSS selector queries."

"OpenAM centralizes authentication by using a variety of authentication modules. Authentication modules connect to identity repositories that store identities and provide authentication services. The identity repositories can be implemented as LDAP directories, relational databases, RADIUS, Windows authentication, one-time password services, other standards-based access management systems and much more."

"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."

"In this section we'll use Finagle to build a very simple HTTP server that is also an HTTP client - an HTTP proxy." Proxy reverso reactivo en un puñado de líneas en scala.

"User-Managed Access (UMA) Profile of OAuth 2.0"

Excelente presentación sobre virtualización y la nube. Imperdible. Incluye transcripción que se puede leer en lugar de ver el video.

"Joyent Triton™ is designed from the ground up to radically simplify container deployments in production, at scale, while delivering enterprise-grade security, software-defined networking, and bare-metal performance. Deploy Triton Elastic Container Infrastructure in your datacenter or leverage the Triton Elastic Container Infrastructure Service in the Joyent Public Cloud."

"Microservices based architectures are not new but are suddenly in the spotlight due to their powerful and sophisticated practices enabling streamlined application development and deployment. However, transitioning from a monolithic approach to a microservices-based architecture requires not only technical expertise, but organizational buy-in as well. In a recent ActiveState webinar, John Wetherill and Phil Whelan discussed a number of tips and tricks to help companies transition to and get the most out a microservices-based approach."

"WSDL2Go code generation as well as its SOAP proxy"

"Leave the hassle of paper behind."

High-Tech Companies Grow Quickly and Efficiently with eSignatures

IBM WebSphere Portal and Web Content Manager Version 8.0.0.1 Reviewer's guide

"Framework for building RESTful API's in Go"

"OSIN is an OAuth2 server library for the Go language, as specified at http://tools.ietf.org/html/rfc6749 and http://tools.ietf.org/html/draft-ietf-oauth-v2-10. Using it, you can build your own OAuth2 authentication service. The library implements the majority of the specification, like authorization and token endpoints, and authorization code, implicit, resource owner and client credentials grant types."

"But when Mark Russinovich, Microsoft's CTO for Azure, took the stage at Build 2015 in San Francisco Wednesday morning to demonstrate how containerized microservices applications work in Windows Server. [...] As is his wont, he dove right in to a demonstration of using Docker Build (on a PowerShell command line) to package and deploy an ASP.NET web site as a Docker container. [...] He took only a few seconds to package the web site into a container image, then he ran the package with the docker run command. [...] And then he paused, took the temperature of the room, and may have recognized that Windows developers may have been completely confused by what they were seeing. [...] So Russinovich asked for a show of hands of folks in the room who might have heard of something called Linux. (Don't worry, he's done this before.) [...] He then used a new build of Visual Studio, running in Windows, to publish the container to the Linux host. He then proceeded to debug the running Linux app, including setting a remote breakpoint, from Visual Studio. [...] Without saying so explicitly, Mark Russinovich was obsoleting much of Windows Server before developers' eyes."