OExchange makes it possible to share any URL-based content with any service on the web. It defines:
A common way for services to receive content, removing any and all service-specific integration requirements A discovery feature so services can publish themselves and their endpoints, making it possible to integrate with services you didn't even know about at development time A decentralized, user-centric model for saving preferred services, making sharing more personal
Assist developers in improving the code of their projects.
Help project managers to meet quality requirements for their applications.
Give top-managers dashboards to monitor the overall health of their information system.
The snapshot archive is a wayback machine that allows access to old packages based on dates and version numbers. It consists of all past and current packages the Debian archive provides.
The ability to install packages and view source code from any given date can be very helpful to developers and users. It provides a valuable resource for tracking down when regressions were introduced, or for providing a specific environment that a particular application may require to run. The snapshot archive is accessible like any normal apt repository, allowing it to be easily used by all.
L'objectif de ce Wiki est de créer de manière collaborative un livre blanc sur le Scrum Product Owner. Il existe très peu de documentation sur le rôle du Product Owner , et encore moins en français.
Tant dans mon métier de Coach que lors de mes interventions (surtout sur le web), je m'aperçois de la nécessité de clarifier Scrum et ses différents rôles. Scrum est une méthode gestion de projet agile ... disciplinée.
Ca fait un petit moment déjà que j'essaie de me créer un environnement de développement distant, c'est à dire que je me connecte sur une machine en ligne pour faire ce que j'ai à faire. C'est assez sympa d'utiliser le protocol NX, il marche bien en plus. Mais je me suis très vite trouné vers une solution entièrement sur un terminal. Je zappe tout ce qui est configuration de screen, mc, finch, irssi etc.. Je vais vous présenter ma personnalisation de vim, un éditeur de texte.
Cacoo is a user friendly online drawing tool that allows you to create a variety of diagrams such as site maps, wire frames, UML and network charts. Cacoo can be used free of charge.
phpCallGraph is a tool to generate static call graphs for PHP source code. Such a graph visualizes the call dependencies among methods or functions of an application. Arrows represent calls from one method to another method. Classes are drawn as rectangles containing the respective methods. The graphs can be leveraged to gain a better understanding of large PHP applications or even to debunk design flaws in them. The example call graph on the right shows the main class of phpCallGraph itself and the internal dependencies among its methods. It is also possible to visualize calls to internal functions of PHP and to some extend call dependencies among different classes. Have a look at the example call graphs to get an impression.
The core of the call graph generator forms an object-oriented PHP5 library, which may also be integrated in other projects. It leverages the InstantSVC CodeAnalyzer and DOT. On top of it, a commandline application allows easy creation of call graphs in various formats, e.g. text, png, jpg or svg. phpCallGraph is free software licensed under GPLv3.
xtractr is a hybrid cloud application for indexing, searching, reporting, extracting and collaborating on pcaps. This enables you to rapidly identify field issues and perform network forensics and troubleshooting with just a few clicks. This lite version of xtractr can index up to 2.5 million packets or 250 Mbytes of pcaps. While xtractr can be used as a standalone application, it works best with Mu Studio to convert the problematic conversation into a stateful test case.
Designed by educators for educators, Sakai is an enterprise teaching, learning and academic collaboration platform that best meets the needs of today's learners, instructors and researchers.
Neo4j is a graph database. It is an embedded, disk-based, fully transactional Java persistence engine that stores data structured in graphs rather than in tables. A graph (mathematical lingo for a network) is a flexible data structure that allows a more agile and rapid style of development. You can think of Neo4j as a high-performance graph engine with all the features of a mature and robust database. The programmer works with an object-oriented, flexible network structure rather than with strict and static tables — yet enjoys all the benefits of a fully transactional, enterprise-strength database.
The world of scalable databases is not a simple one. They come in every race, creed, and color. Rick Cattell has brought some harmony to that world by publishing High Performance Scalable Data Stores, a nicely detailed one stop shop paper comparing scalable databases soley on the content of their character. Ironically, the first step in that evaluation is dividing the world into four groups:
Key-value stores: Redis, Scalaris, Voldmort, and Riak. Document stores: Couch DB, MongoDB, and SimpleDB. Record stores: BigTable, HBase, HyperTable, and Cassandra. Scalable RDBMSs: MySQL Cluster, ScaleDB, Drizzle, and VoltDB. The paper describes each system and then compares them on the dimensions of Concurrency Control, Data Storage Replication, Transaction Model, General Comments, Maturity, K-hits, License Language.
Request Queuing allows your system to operate at optimal throughput. In the above example : the optimal throughput was at 500 concurrency. The concurrency at which optimal throughput is achieved is usually right below where exponential degradation starts to take place. At all times the system was operating at this optimal throughput Your users only experience linear degradation versus exponential degradation. As shown in the diagram, with no request queueing your users and your system would have experienced exponential degradation after 500 requests. Requests 0-500 take 1 second, 501-1000 takes 2 seconds, 1001-1500 take 3 seconds and so on – With Request queueing – the response times become linear Your system experiences NO degradation – This is worth repeating. The system is always operating at an optimal throughput. The only attribute that is dynamic is the queue size. The system remains in the green zone as highlighted in the diagram.
