Hi, Hopefully most of the people from mod_perl who were interested in this discussion have signed up by now.
My proposals are down below. You can safely delete this message and read it all at http://www.officevision.com/pub/p5ee/ I have copied and pasted it here for your convenience and to allow email replies to the contents. Stephen ---------------------------------------------------------------------------- ---- P5EE - Perl 5 Enterprise Extensions ---------------------------------------------------------------------------- ---- Other P5EE Pages This page represents my (Stephen Adkins) understanding of what P5EE should be. This is not the authoritative P5EE page as though there were only one. Links to pages describing other people's visions of P5EE are shown below. * none yet Mission and Vision The mission of the P5EE initiative is to facilitate the development, deployment, and promotion of Enterprise Systems writtin in Perl. This involves the following elements in its vision. * Architects, Designers, and Developers should have easy access to the tools, techniques, and guidelines to write enterprise software in Perl. * System Administrators should have the knowledge to install and operate enterprise systems which include enterprise applications written in Perl. * IT managers should have confidence in hiring enterprise architects who specialize in Perl, in supporting enterprise development projects in Perl, and in deploying enterprise applications in Perl. Definitions Enterprise Systems are systems which have the attributes enumerated below. When systems have these attributes, they are such that large enterprises can invest substantial corporate resources in them. * Scalability - the ability to support the required quality of service as the load increases * Maintainability - the ability to correct flaws in the existing functionality without impacting other components/systems * Reliability - the assurance of the integrity and consistency of the application and all of its transactions. * Reliability spans from the OS to the Application to the service provided. * Availability - the assurance that a service/resource is always accessible * Extensibility - the ability to add/modify functionality without impacting existing functionality * Manageability - the ability to manage the system in order to ensure the continued health of a system with respect to scalability, reliability, availability, performance, and security. * Portability - the ability of the software to run on a variety of hardware and operating system configurations * Interoperability - the ability of the system to share data with external systems and interface to external systems * Accessibility - the ability to access system functions through different user agents and in different languages Perl 5 Enterprise Extensions are the set of Perl Modules which can be used to build Enterprise Systems when P5EE guidelines are followed. Philosophy Perl Modules on CPAN are flexible, supporting many different designs. CPAN supports many redundant modules. In fact, the slogan in Perl is "there is more than one way to do it" (TMTOWTDI). Developing an Enterprise System is different. It requires many consistent design choices. It requires the successful integration of numerous perl modules. The slogan in P5EE should be "this is one great way to do it". The fact is that there may be many great ways to do it. P5EE should support multiple expressions of "the right way to do Enterprise development in Perl". Let the winners and losers emerge over time as support waxes or wanes for one approach or the other. (See also my original write-up, linked from http://www.officevision.com/pub/p5ee/.) P5EE Artifacts The following artifacts of the P5EE initiative should emerge from the community as a whole. * A list of computing technologies and techniques (i.e. RDBMS/SQL, HTTP, HTML, XML, SOAP, etc.) * For each technology/technique, the list of perl Modules that are useful to evaluate. This should include each module that at least one member of the list believes should be considered the general consensus is that the module is an excellent candidate * A sample Enterprise application specification (something better than a pet store). This should be genuinely useful (so that people start installing it and using it), simple (so that we don't expend too much energy on a demo), and architecturally demanding (so that we exercise and demonstrate nearly the full feature set of P5EE) * A self-training curriculum for developers to become "self-certified" as Enterprise Perl Developers, Enterprise Perl Architects, and Enterprise Perl Administrators. The following artifacts should emerge from each group of people who roughly agree on an approach to P5EE. * The list of Perl modules used (addressing each of the technologies/techniques) * A software layer architecture diagram (layers of software within a process) * A process architecture diagram (processes communicating within and between machines) * A systems architecture diagram (showing machines filling roles on a network) * A set of guidelines to Enterprise Perl Administrators on how to configure systems and install software to prepare for enterprise development and deployment. * A set of guidelines to Enterprise Perl Architects and Developers on how to design and develop a system * A set of guidelines to Enterprise Perl Administrators on how to operate and administer a running system * Actual software implementing the sample application The existence of actual running code will do much to demonstrate the techniques described in the guidelines, give a good History, Background, Prior Discussions, Prior Work (see http://www.officevision.com/pub/p5ee/ for links) * if anyone knows more resources on the web, please email me at [EMAIL PROTECTED] * Oct 2001 P2EE discussion thread on mod_perl list * Aug 2001 P2EE discussion thread on mod_perl list - [more] * Perrin Harkin's write-up of a high-volume installation of mod_perl at E-Toys and discussion
