By Juergenkress-Oracle on Nov 17, 2015
This blog article is the second of a three part series which describes how FlexDeploy enables the transition from running your Java applications on-premise to running them on the Oracle Java Cloud Service. The first article in the series focused on moving applications from on-premise to the cloud (i.e. “lift and shift”). This article will explore how FlexDeploy fosters another important facet of cloud computing – utilizing dynamic capacity to reduce cost. There are two aspects to dynamic capacity: quickly spinning up and tearing down cloud environments on-demand, and “turning off” environments when not in use to more effectively manage subscription costs. The Oracle Cloud Services enable both aspects, but for the purpose of this blog article we will focus on the later.
Certain environments during the dog days of the software development lifecycle can be utilized nearly 24×7. However, most organizations have environments that are not used quite so regularly. This may be test environments that are only utilized during the day, user acceptance testing environments that are only used during the later end of the release lifecycle, or in support environments that are only utilized to troubleshoot reported production problems. When you purchase an hourly subscription to Oracle Cloud Services you only pay when the environments are up and running. So effectively managing when the environments are running can produce a huge cost savings year over year. The remainder of this article will demonstrate how FlexDeploy can help manage this dynamic capacity more effectively.
Using the Java Cloud Service console I have provisioned 6 instances. A DEV, QA and PRODUCTION instance for managing the entire software lifecycle of our Payroll applications, and a DEV, QA and PRODUCTION instance for managing our Purchasing applications. In FlexDeploy terminology that relates to following constructs:
· 3 Environments (DEV, QA and PRODUCTION)
· 2 Instances (PAYROLL and PURCHASING)
Each FlexDeploy environment instance defines the properties required to connect to its associated Java Cloud Service instance. Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.