Performance Co-Pilot (PCP) is a framework and set of services for supporting system-level performance monitoring and performance management. It provides a unifying abstraction for all of the interesting performance data in a system, and allows client applications to easily retrieve and process any subset of that data using a single API. A client-server architecture allows multiple clients to monitor the same host, and a single client to monitor multiple hosts. Archive logging and replay are integrated so that a client application can use the same API to process real-time data from a host or historical data from an archive.
GraphicsMagick is a robust collection of tools and libraries which support reading, writing, and manipulating an image in over 90 major formats including popular formats like DPX, DICOM, BMP, GIF, JPEG, JPEG-2000, PDF, PNG, PNM, SVG, and TIFF. A high-quality 2D renderer is included, which provides a subset of SVG capabilities. C, C++, Perl, Tcl, and Ruby are supported. Originally based on ImageMagick, GraphicsMagick focuses on performance, minimizing bugs, and providing stable APIs and ABIs. It runs on all modern variants of Unix, Windows, and Mac OS X.
Jmx4Perl provides an alternate way of accessing Java JEE Server management interfaces that are based on JMX (Java Management Extensions). It is an agent-based approach where a small Web application deployed on the application server provides HTTP/JSON-based access to JMX MBeans registered within the application server. It is set up from a handful of Perl modules, which can be integrated seamlessly in your own programs. It also includes a Nagios plugin, check_jmx4perl, a jmx4perl command line tool for remote JMX queries and operations, and a readline-based JMX shell j4psh, with context sensitive command completion and syntax highlighting.
Schedule::Cron is a Perl module that provides a simple but complete cron-like scheduler. It can be used for periodically executing Perl subroutines. The philosophy behind Schedule::Cron is to call subroutines periodically from within one single Perl program instead of letting cron trigger several (possibly different) Perl scripts. Everything under one roof. Furthermore, Schedule::Cron provides a mechanism to create crontab entries dynamically, which isn't that easy with cron. It knows about all extensions (at least all extensions the author is aware of, i.e those of "Vixie" cron) for crontab entries like ranges including 'steps', specification of month and days of the week by name, or coexistence of lists and ranges in the same field. It even supports a bit more (like lists and ranges with symbolic names). It has existed since 1999 on CPAN and is successfully used in many projects.
PDF::API2 is 'The Next Generation' of Text::PDF::API, a Perl module-chain that facilitates the creation and modification of PDF files. It features support for the 14 base PDF Core Fonts, TrueType fonts, and Adobe-Type1, with unicode mappings, embedding of bitmap images, compression via zlib, and a rich object-oriented API.
Berkeley DB XML is a native XML database engine for use within your product. Made available as a C++ library with language bindings for Java, Perl, Python, PHP, and Tcl, it integrates directly into your application (it is not a standalone database server). It provides XQuery access into a database of document containers. XML documents are stored and indexed in their native format using Berkeley DB as the transactional database engine.
Catalyst is a Web application framework for Perl. It is based on Maypole, and adds many features from Ruby on Rails, Struts, Spring, and Tomcat. The development philosophy focuses on Don't Repeat Yourself, Lego-like components, Code Generation, and very strong testability. It supports a number of plugins, models, views, and controllers.
AnyEvent provides an identical interface to multiple event loops. This allows module authors to utilize an event loop without forcing module users to use the same event loop (as only a single event loop can coexist peacefully at any one time). The interface itself is vaguely similar but not identical to the Event module. On the first call of any method, the module tries to detect the currently loaded event loop by probing for an already-loaded event loop, such as Glib or Event. The first one found is used. If none is found, the module tries to load an event module, and failing that, it will fall back to an optimized pure Perl implementation.