Oracle OpenWorld 2012 conference is in its full swing in San Francisco. More than 50.000 attendees from over 123 different countries registered for the conference and they have more than 2.500 available sessions to attend. More interesting facts about the conference can be found here: https://blogs.oracle.com/oracleopenworld/entry/oracle_openworld_by_the_numbers
The conference kicked off on Sunday, September 30, when Oracle’s CEO Larry Ellison announced several new services. To existing PaaS and SaaS offering under Oralce Cloud, a new IaaS offering is available. Oracle Cloud also got an extension called Oracle Private Cloud. It provides clients with the same functionality as in the public cloud offering, but the location for hardware is provided by clients. Hardware is owned and managed by Oracle. Following the Private Cloud announcement, Ellison announced Oracle Database 12c, as the first multitenant database. The last major announcement was Exadata X3 Database In-Memory Machine. It uses 26 terabytes of memory and is designed to store entire databases in memory. Larry also gave a talk on Tuesday’s keyword informing the public about the importance of underlying cloud infrastructures on which SaaS applications are running. He pointed out that they are the only cloud provider who is giving their customers the choice of deployment. He predicted that many on-premise customers will move to the Oracle public cloud in the future.
For other information about the Oracle Open World conference visit the conference web site: http://www.oracle.com/openworld/index.html
In parallel to the Oracle OpenWorld 2012, Java One 2012 conference is taking place. Feel free to explore its website: http://www.oracle.com/javaone/index.html
Early this year Amazon introduced a new service, Elastic Beanstalk. It enables quick Java application deployment and management without having to worry about the infrastructure that runs these applications. When application is created you simply upload new application version. After the upload, Elastic Beanstalk will automatically create and configure AWS resources and services such as Amazon Elastic Compute Cloud (EC2), Amazon Simple Storage Service (Amazon S3), Amazon Simple Notification Service (Amazon SNS), Amazon CloudWatch, Elastic Load Balancing and Auto Scaling in order to run the application. These automatically configured resources to run the application version can also be called environment. Although the environment is configured automatically, you still retain full control of resources representing it.
On June 30th Amazon announced two new capabilities of Elastic Beanstalk. Now it is possible to save an environment configuration and launch new environments with a saved configuration, or apply a saved configuration to an existing configuration. This feature makes it easy to launch multiple environments with preferred settings. The second capability allows you to swap URLs between environments. This is especially useful for staging new application versions. It enables you to create a new environment for new application version and when it is ready for production, you simply swap URLs. This way user does not experience any downtime when upgrading applications.
Scalability in general can be achieved through vertical or horizontal scaling. Vertical scaling also known as scaling up means adding more resources to the same machine. Horizontal scaling is also known as scaling out, which means creating more instances of the same machine. Scaling in IaaS Cloud is typically achieved through horizontal scaling. This can be done manually by users provisioning new virtual machines or automatically according to certain infrastructure metrics. Capacity provisioned this way can never exactly fit the software needs and that is why vertical scaling is a very desirable feature to be supported by IaaS Cloud. With automated vertical scaling, more memory and CPUs could be added to the virtual machines on the fly. Capacity provisioned this way would better fit the software needs.
Adding memory and CPU on the fly is often referred to as hot add. Windows operating systems supporting this feature are listed below. None of them supports hot removal of memory or CPUs. On the other hand hot adding and removing CPUs and memory is well supported in Linux operating systems – especially in newer versions of the Linux kernel.
|Operating system||Hot add memory||Hot remove memory||Hot add CPU||Hot remove CPU|
|Linux OS with CPU hotplug and memory hotplug support (SLES 11, RHEL 6, and others)||Yes||Yes||Yes||Yes|
|Windows Server 2008 Datacenter Edition R2 x64||Yes||No||Yes||No|
|Windows Server 2008 Enterprise Edition R2 x64||Yes||No||No||No|
|Windows Server 2008 Datacenter Edition x64||Yes||No||Yes||No|
|Windows Server 2008 Datacenter Edition x86||Yes||No||No||No|
|Windows Server 2008 Enterprise Edition x64||Yes||No||No||No|
|Windows Server 2008 Enterprise Edition x86||Yes||No||No||No|
|Windows Server 2003 Enterprise Edition x64||Yes||No||No||No|
|Windows Server 2003 Enterprise Edition x86||Yes||No||No||No|