For many, building high performance applications that make use of relational persistence automatically mean building something from scratch using straight JDBC calls. Frankly, in some domains and applications this is absolutely the correct thing to do. Many developers struggle with persistence layer performance and therefore assume they need to revert back to a time consuming and maintenance prone custom solutions.
This session will enlighten those who feel they “should” be able to use a persistence layer for their application, but just can’t seem to get the kind of performance they require. We will review many important performance traps such as indirection (aka proxies/just in time reading), inheritance, locking and long-lived transactions. We will discuss many overlooked performance benefits of persistence layers such as advanced caching, N+1 read avoidance, and projections. We will also look at how to tailor your application to leverage database specific optimizations such as “hints”, custom types and how to handle XML.
Prerequisite: basic understanding of Persistence Layers, Java and Relational Databases
Even after almost a decade of existence, Java Developers still haven’t mastered the politics of persistence. The DBA’s rule the roost in most Fortune 500 and Global 2000 organizations, and many Java developers have run smack damn into a brick wall asking their Database Admin to make even a minor change to the schema.
In organizations where DBA’s aren’t exercising their apparent narcissistic rights, Java developers sometimes rule the database. This often leads to the formation of a “Lord of the Flies” culture. The result? Chaos. Want proof? Just look at the web of homegrown solutions, fights over persistence specifications and approaches that have been developed over the past decade.
This lighthearted session will first discuss the “Java Developer VS DBA” debates that continue to occur, especially in larger organizations. The presenter is uniquely qualified to make fun of both OO developers (having been one since birth) and DBAs (being an Oracle employee). Once divulging the best strategies for asking a DBA to bastardize her database, we will turn our attention to the “Lord of The Flies” culture that has emerged in many unchecked organizations.
Prerequisite: basic understanding of Java and Relational Databases
Donald Smith is a Director of Technology at Oracle Corporation. Donald has extensive field experience focusing on persistence projects, including object-relational and other architectures. He brings together a decade of experience with customers and projects from around the world, from small "dot-com" through Fortune 50 companies. Donald speaks regularly about persistence, business integration and politics at conferences and events world wide, including Java One, Oracle World, Sun Tech Days, OOPSLA, JAOO, Server Side Symposium, Colorado Software Summit and others.