Getting Startedwith pureQuery

Chapter 1 – Introduction to pureQuery 31
test their applications using dynamic SQL, and with no additional changes, that same
application can be bound and take advantage of the performance, security, and stability of
static SQL execution (described in Appendix D).
Note:
If you are not familiar with static SQL and the benefits of using it, see Appendix D or the
article entitled No excuses database programming for Java at
ibm.com/developerworks/data/library/dmmag/DBMag_2008_Issue2/NoExcusesDB/
The pureQuery APIs are designed with Web 2.0 in mind -- custom result handlers map
results to plain old Java objects (POJOs), XML, or JavaScript Object Notation (JSON).
In addition to improved ease-of-use, performance is easier to build into the application
using pureQurey. For example, it’s easy to specify retrieval of only the first row of results,
to reduce network and processing time for time-critical user interfaces. Other options for
reducing network cost include the use of batching updates across tables, known as
heterogeneous batching, and by the ability to query and join across in memory Java
collections and the database.
1.3 pureQuery runtime
The pureQuery runtime is the engine that provides improved performance, security, and
manageability and is delivered in the product Optim pureQuery Runtime. You deploy the
runtime on the application server (or wherever the application runs). The pureQuery
runtime provides flexible access from a wide variety of frameworks and data access
mechanisms, as shown in Figure 1.2.