Group items tagged

"LiMux - The IT evolution is a project by the city of Munich (third-largest city in Germany) to migrate their software systems from closed-source, proprietary Microsoft products to free and open-source software. The project was successfully completed in late 2013, which involved migrating 15,000 personal computers and laptops of public employees to free and open-source software."

"In Forrester's 40-criteria evaluation of application programming interface (API) management solutions, we identified the 11 most significant software providers in the category - 3scale, Apigee, Axway, CA Technologies, IBM, Informatica, Intel Services, MuleSoft, SOA Software, Tibco Software, and WSO2 - and researched, analyzed, and evaluated them. This report details our findings about how well each vendor's products fulfill our criteria and where they stand in relation to each other. This analysis, combined with three buying guides that highlight key make-or-break decision factors, will help AD&D professionals select the right partner for their API management needs."

"Introduction In the modern era, software is commonly delivered as a service: called web apps, or software-as-a-service. The twelve-factor app is a methodology for building software-as-a-service apps that: Use declarative formats for setup automation, to minimize time and cost for new developers joining the project; Have a clean contract with the underlying operating system, offering maximum portability between execution environments; Are suitable for deployment on modern cloud platforms, obviating the need for servers and systems administration; Minimize divergence between development and production, enabling continuous deployment for maximum agility; And can scale up without significant changes to tooling, architecture, or development practices. The twelve-factor methodology can be applied to apps written in any programming language, and which use any combination of backing services (database, queue, memory cache, etc). Background The contributors to this document have been directly involved in the development and deployment of hundreds of apps, and indirectly witnessed the development, operation, and scaling of hundreds of thousands of apps via our work on the Heroku platform. This document synthesizes all of our experience and observations on a wide variety of software-as-a-service apps in the wild. It is a triangulation on ideal practices for app development, paying particular attention to the dynamics of the organic growth of an app over time, the dynamics of collaboration between developers working on the app's codebase, and avoiding the cost of software erosion. Our motivation is to raise awareness of some systemic problems we've seen in modern application development, to provide a shared vocabulary for discussing those problems, and to offer a set of broad conceptual solutions to those problems with accompanying terminology. The format is inspired by Martin Fowler's books Patterns of Enterprise Application Architecture and Refactoring. Who should

Bueno. Eso. Compartí el que me di cuenta que puso antes Pablo en vez del original por error, pero la idea entre ambos, si la obviedad es tolerable, es idéntica :) Está muy bien estructurado en cuanto que cada factor depende de los demás a la vez que los promueve. Permite un enfoque general que incluye prácticas de arquitectura - y de armado cotidiano de productos - que posibilitan llegar donde yo entiendo - según me voy enterando - que es el lugar a donde llegar. Sin embargo, creo que ni éste departamento en sus sistemas más nuevos cumple todos y cada uno de aquellos factores. Esto, lejos de ser una crítica, es una invitación para que revisemos si es el único método posible - cosa improbabilísima - o el mejor método - también bastante improblable - a seguir. Lo que sí sostengo como un absoluto - quien no lo haría - es que es un método practicable. Mi aporte mínimo es defenderlo como uno bueno.

"Ford noted the growing relationship between software architecture and DevOps. The interdependence of the two disciplines is evident within Ford's company: "One of the things that we're really adamant about now," he said, "is that someone from DevOps and operations should be a full-time member of a software development team … you cut way down on churn and other sorts of useless engineering activities.""

"El Catálogo de Software Público es una colección de enlaces a software, plataformas, APIs y otros recursos desarrollados por la administración pública."

"Phabricator is a collection of open source web applications that help software companies build better software."

SoftNAS™ is business-class network attached storage (NAS) delivered as software as a service.  The NAS software virtual appliance runs within your cloud computing environment (e.g., Amazon EC2) or local virtual server environment (e.g., VMware vSphere) and manages the available raw disk storage, providing enterprise-grade storage capabilities. SoftNAS leverages a number of open source technologies, including ZFS on Linux.  ZFS on Linux is a port of the popular ZFS filesystem originally produced by Sun Microsystems and released with OpenSolaris.  SoftNAS builds on the robust, solid foundation of ZFS and its powerful, extensible Linux foundation.

"Bintray is a social service for developers to publish, download, store, promote, and share open source software packages. With Bintray's full self-service platform developers have full control over their published software and how it is distributed to the world."

"In an indication of how rapidly the containerized technology ecosystem is metastasizing, SocketPlane.io - a startup venture founded just last October with the goal of building a controller-less software-defined network model for Docker environments - is being acquired by Docker, Inc., the two organizations jointly announced Wednesday morning. SocketPlane creates a networking abstraction for Docker containers at the socket layer. It connects containers without the need for a network controller, either physical or virtual. Put another way, it facilitates a software-defined network by letting the containers be the network."

"What is Aurora? Platforms like Twitter operate across tens of thousands of machines, with hundreds of engineers deploying software daily. In this type of environment, automation is critical. Aurora is software that keeps services running in the face of many types of failure, and provides engineers a convenient, automated way to create and update these services. To accomplish this, Aurora leverages the Apache Mesos cluster manager, which provides information about the state of the cluster. Aurora uses that knowledge to make scheduling decisions. For example, when a machine experiences failure Aurora automatically reschedules those previously-running services onto a healthy machine in order to keep them running."

Herramienta para análisis y documentación de toma de decisiones de arquitectura de software. 

The required techniques of effective reasoning are pretty formal, but as long as programming is done by people that don't master them, the software crisis will remain with us and will be considered an incurable disease.

"A community driven list of useful Scala libraries, frameworks and software."