ORM tools are here to stay, at least for a few years until the next big thing. So is Cloud. Both concepts spin the line that specialist skills at the database and operations layer are not needed. DBAs need to take this on board and work out how they can add value in this new paradigm, or risk being seen as no longer needed.

ORM and Cloud will move forward by dealing with some low hanging fruit. Third-party applications where the customer has little ability to change anything are prime candidates for Cloud. Small scale apps where ORM database inefficiencies do not cause SLAs to be breached are also headed for the Cloud. This results in a large mass of applications that have a significantly lower development and operational cost than traditional 'optimised' applications, and businesses will be keen to see these cost savings across all applications.

The fact that some applications perform very poorly using the ORM model may become a driver for the business to find an alternative app that can get the Cloud and ORM savings, rather than be a reason for keeping the original application. This could be particularly true if the application is not essential to the main business profit drivers.

IMHO database professionals need to focus on adding value to the key profit drivers, and how they can minimise costs for everything else. For many people, even finding out what drives their employer's profits will be something new, while others will already be working on these lines.