Change is the big word at Oracle Open World. The movement of on-premise towards cloud is a big change for the customers and partners but also for Oracle itself. As Oracle has shifted gears towards maximum Cloud usage in a short timeframe this has impact on all sorts of areas. With my visit to Oracle Open World this year I hear the term Paradigm Shift a lot of times, here my summary of these areas.
End-user paradigm shifts
What is going to change for end-users has already been described over the last years in many books, blogs, articles etc. Things like anytime, anytime access to all data and functionality, agility of delivery of new products, different payment models, complete different admin approach are only a few to mention the big impact of Cloud on the end-users and to the market itself.
Oracle Paradigm shifts
From waterfall towards Agile delivery
Oracle is moving from a rigid long term release delivery organisation, with release delivery cycles of 4-5 years, towards a short cycled agile organisation aiming for bi-weekly release deliveries. As with every organisation changing towards Agile delivery, this is not done on one go. So everyone in de product delivery organisation at Oracle is telling the same story, ‘We’re on a journey, and learning along the way..’.
Build for business instead of for IT.
The message that all cloud development teams received is that their product should be used by a simple business user and adjustable by a simple business owner. So in every presentation the key message is focused on how the products support the day in a life of a business owner in the best suitable way. One of the Cloud presentations I attended started with 'Instead of talking about the products themselves we’d like to talk about how to use the products'. Oracle is now talking in business scenario's instead of product features, knowing Oracle a bit for many years this is indeed a change.
Partner paradigm shifts
Speed of delivery over robustness (?)
With the advent of new languages such as Node.js and Angular we help he developers with tools that are aimed at extreme speed of delivery, enabling beautiful cloud based mobile application in a short timeframe. This comes however with a price, and that can be robustness of the application. Front-end integration towards apps, with no XML inclusion, gain a lot from speedy languages. Back-integration with the focus on stable XML based integration need support from stable Java based solutions contains translation via XSLT and the likes. As always 'if all you have is a hammer, everything looks like a nail’. Agile teams delivering integration in a variety of use cases including front-end and back-end integration might turn to the easy way Node.js based integration, just to ensure a delivery in a short timeframe.
The boundaries when using the different languages in the landscape must be clearly set, executed by the teams, and controlled by QA teams. The fact that you need to deliver fast, does not mean that you are allowed to compromise the quality of the application.
Applying templates towards coding
Coding is moving to applying templates and adjusting towards the business needs. Each PaaS Cloud product contains a pattern library, that enable fast delivery, and this library will grow with every release. Partners can bring in their project experiences as templates into the marketplace. At this moment the marketplace is not *yet) connected to the cloud products. Change from coding towards template based delivery impacts hugely the design time aspect of projects, and will result in shorter timeframe for implementation. As a result System Integrators (SI’s) will shift more towards IP driven Independent Software Vendors (ISV’s).