ABSTRACT
Best practices for using SQL and PL/SQL only (with HTML, XML via PSP, or Web Toolkit)
Best practices for using .NET based languages (C++, C#)
Best practices for using Java-based languages (Java Libraries, Java via JDBC, Java via SQLJ, Java via Java Stored Procedures)
Best practices for using PHP-based languages (PHP-only, PHP and AJAX, PHP Web pages)
Perl in the picture-best practices for the perfect fit and use of Perl in an embedded scenario
For better or worse: Application-centric and business-centric key performance indicators
A best-practice strategy for choosing and determining the suitability of an embedded programming solution is governed by a set of essential factors that serve as evaluation criteria for the solution being proposed. These are generic in nature and apply to any technology, architecture, and methodology in consideration, whether it is Java-based, .NET-based, PHP-based, Perl-based or solely Oracle-based (using SQL and/or PL/SQL in conjunction with HTML/ XML). These can be grouped into the following major categories:
The
purpose of the proposed solution
in terms of software pragmatics; that is, a generic solution that is more like a product in broad terms, a customer-centric solution, a benchmarking solution (that eventually would evolve into a product or software application),
an architectural blueprint (that can be enhanced/extended), and so on.
