On-demand Webinar: Containerizing Oracle: Not Thinking About It Yet? You Should Be!
Still running your databases on underutilized bare metal servers? Looking to consolidate your databases and reduce license costs, but not create an OS sprawl? If the answers are YES, then watch this on-demand webinar to see how Linux container technologies like docker and LXC can help.
We explore how to use containers to consolidate databases without compromising performance, while guaranteeing isolation and no manageability changes. We examine and contrast other prevalent consolidation approaches, along with the roadblocks they present and how containerization helps you overcome those problems.
We show you how to:
- Configure an Oracle database on LXC
- Apply IO resource management on your Oracle database running in a container
- Simplify database lifecycle management tasks with single click clone, time travel
The core elements are:
- Data Sharing
Storage: How do I configure storage for the Oracle database running in a Docker container?
In my opinion, this is probably the most important question when considering running an Oracle database using Docker. Running a database in a container actually provides the unique opportunity to decouple the compute from the storage.
QoS: How do I consolidate without worrying about noisy neighbors?
One of the key virtues of virtualization is the ability to share the system resources across many applications. While traditional VM based virtualization has seen some adoption in Dev and Test systems, the inability to ensure predictable performance has forced enterprises to use bare metal servers for production databases.
Data Sharing: How do I share data across environments?
I am often asked this or a slight variation of this question – “Will I be able to share data across Dev and Test environments if I run my application database using Docker?” The answer is Yes, if you plan and configure your storage correctly.
Availability: Can I ensure application availability across machine failures?
As I mentioned above, handling failover or relocation (read as managed failover) of the database instance by moving the container from one host to another is a very important requirement for running databases in general. Today a similar capability exists in RAC One but it requires a dedicated and often an idle machine for instance failover. Not to mention the extra license cost.