The most valuable features of Oracle Java Cloud Service is the ability to develop applications on-premise, using well know IDEs (Oracle JDeveloper in our case) with the possibility to quickly deploy it to the cloud-based WebLogic Server. Also, the possibility to run applications that were initially deployed to IBM WebSphere albeit with some re-configuration and adjustments.
Fast, rapid and agile development and deployment of an ADF application (within Proof-of-Concept project) involves four developers in a distributed team (across two different time-zones) and through this they are able to cooperate quickly, without the usual problems of dev/test environment deployments.
We now have the ability to very quickly develop/modify and deploy applications (e.g. Proof of Concept, demos etc.) with a geographically distributed team using agile methodologies whilst avoiding environment specific problems such as long-time delays to restore an environment at a specific point in time, at the same time.
It needs to have the ability to create a service with the same name as another one when the initial creation failed as sometimes it's necessary to have a service with exact name. As far as I know, this problem is indicated as a "known issue" by Oracle, but this point is really needed sometimes.
You need to look into the Oracle Coherence optional offer as the description is not absolutely clear in some of the articles for beginners.
We use this for building extensions to Oracle CX. Very easy to deploy applications.