Group items matching

in title, tags, annotations or url

What is Graphite? Graphite is a highly scalable real-time graphing system. As a user, you write an application that collects numeric time-series data that you are interested in graphing, and send it to Graphite's processing backend, carbon, which stores the data in Graphite's specialized database. The data can then be visualized through graphite's web interfaces. Who should use Graphite? Graphite is actually a bit of a niche application. Specifically, it is designed to handle numeric time-series data. For example, Graphite would be good at graphing stock prices because they are numbers that change over time. However Graphite is a complex system, and if you only have a few hundred distinct things you want to graph (stocks prices in the S&P 500) then Graphite is probably overkill. But if you need to graph a lot of different things (like dozens of performance metrics from thousands of servers) and you don't necessarily know the names of those things in advance (who wants to maintain such huge configuration?) then Graphite is for you.

"URI.js is a javascript library for working with URLs. It offers a "jQuery-style" API (Fluent Interface, Method Chaining) to read and write all regular components and a number of convenience methods like .directory() and .authority(). URI.js offers simple, yet powerful ways of working with query string, has a number of URI-normalization functions and converts relative/absolute paths. While URI.js provides a jQuery plugin. URI.js itself does not rely on jQuery. You don't need jQuery to use URI.js"

Hola!. La vi el viernes a la manyana la libreria esta.Parece que esta buenisima. respecto a lo que yo tenia que hacer obviamente que puede ayudar con las funciones relative y absolute, pero por lo que definimos, "Construir las url's de los recursos a partir del raiz de la libreria", descarte su adopcion por parecerme de alguna forma "sobrecarga".Sea como sea, es una buena herramienta para adoptar. Buen finde.

Me acabo de dar cuenta.... Este articulo lo pusiste el 4. Estamos a la noche del 5 y recien me notifico. No es la primera vez, y ahora sospecho que son todas las veces las que cosas compartidas en diigo que se notifican con demora. Porque sera?

"MaestroNG, an orchestrator of Docker-based deployments. The original Maestro was developed as a single-host orchestrator for Docker-based deployments. Given the state of Docker at the time of its writing, it was a great first step towards orchestration of deployments using Docker containers as the unit of application distribution. Docker having made significant advancements since then, deployments and environments spanning across several hosts are becoming more and more common and are in the need for some orchestration. Based off ideas from the original Maestro and taking inspiration from Docker's links feature, MaestroNG makes the deployment and control of complex, multi-host environments using Docker containers possible and easy to use. Maestro of course supports declared dependencies between services and makes sure to honor those during environment bring up. MaestroNG is, for now, a command-line utility that allows for automatically managing the orchestrated deployment and bring up of a set of service instance containers that compose an environment on a set of target host machines."

"Knative provides a set of middleware components that are essential to build modern, source-centric, and container-based applications that can run anywhere: on premises, in the cloud, or even in a third-party data center. Knative components are built on Kubernetes and codify the best practices shared by successful real-world Kubernetes-based frameworks. It enables developers to focus just on writing interesting code, without worrying about the "boring but difficult" parts of building, deploying, and managing an application."

"Unlike most client libraries dealing with HAL REST APIs, Hybind provides a high-level approach similar to what Object Relational Mapping (ORM) frameworks are for databases. When using Spring Data REST in the server, it is amazing how the amount of code to write is reduced to a minimum. However, a significant amount of repeated boilerplate is still required in the JavaScript client to manipulate the resources and map them to the client-side model. That's why this library exists. It enriches plain JavaScript objects with a convenient API so that performing REST requests is as easy as calling methods directly on the model objects. It is optimized for Spring Data REST, but should work with other HAL APIs following similar conventions."

Muy buen artículo sobre todo si se lee desde punto de vista mas general que junit+java. Me gustó particularmente la cita: "It's overwhelmingly easy to write bad unit tests that add very little value to a project while inflating the cost of code changes astronomically."

"What is the reason to quote at all? Consider it. It shouldn't be to allow people to scroll down to see all earlier discussions. If the news client is a bit smart, fetching the older articles from the server should be just as easy as to "scroll down". If a thread goes forth and back some times and earlier quotes accumulate, an article including all those quotes might get five-ten times larger than a posting without quotes, this wastes bandwidth and hard disk space. Therefore, IMHO, no quotes are far better than a posting at the top of all old quotes."

Una simple traducción de este post podría ser nuestra largamente necesitada convención sobre cómo escribir los comentarios de commits.

"Babel is a JavaScript compiler. Use next generation JavaScript, today."

"I have two claims of which I would like to convince you today: The notion of the networked application API is an unsalvageable anachronism that fails to account for the necessary complexities of distributed systems. There exist a set of formalisms that do account for these complexities, but which are effectively absent from modern programming practice."

The [docker registry](https://registry.hub.docker.com/) is bursting at the seams. At the time of this writing, a search for "node" gets just under 1000 hits. How does one choose? ## What constitutes a good docker image? This is a subjective matter, but I have some criteria for a docker image that I consider good: * **working**.