Oracle 19c's Multitenant Container Architecture and Big Data

Oracle 19c's Multitenant Container Architecture and Big Data

Sikha Bagui, Mark Rauch
Copyright: © 2023 |Pages: 27
DOI: 10.4018/978-1-7998-9220-5.ch031
OnDemand:
(Individual Chapters)
Available
$37.50
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

This article presents a review of several improvements made in Oracle 19c's multitenant container architecture and how these improvements aid in the management of big data from the perspective of application development. With the introduction of this new multitenant container architecture, Oracle's ability to handle big data is drastically improved. The added functionality that comes with the integration of big data platforms, alongside the flexibility and improvement that comes with container databases and pluggable databases, that are the main tenants of Oracle 19c's multitenant architecture, has not only allowed Oracle to stay relevant, but has moved it to the forefront of its competitors.
Chapter Preview
Top

Background: Traditional Oracle Architecture

Oracle databases traditionally consist of at least one database instance. The database itself is a set of files that store its data, and these files can exist independently of the database instance. The database instance is a set of memory structures called the system global area (SGA) and a set of background processes. The instance can exist independently of the database files. When a user connects to the Oracle database, a client process is created with its own server process. Each server process has its own private session memory known as program global area (PGA) (Oracle® Database. Database Concepts,” 2021). It is through the application that interactions are made across either multiple logical databases within a single physical database, or a single logical database distributed across multiple physical databases (Oracle® Database. Database Concepts,” 2021). Each of these memory structures have far more depth to them inclusive of the many different processes hosted within. This traditional structure has been deprecated in favor of a new one, hence the focus of this chapter.

Key Terms in this Chapter

Container Database: A container database can contain either zero, one, or many pluggable databases.

Container: Containers are a bundled unit of software with all their dependencies.

MapReduce: An engine that provides the platform for massive parallel execution of algorithms written in Java.

Big Data: Data that contains greater variety, arriving in increasing volumes and with high velocity.

Multi-Tenant Architecture: Multi-tenant architecture allows multiple users to share a single instance of a software application and its underlying resources.

Container Architecture: Container architecture is a logical collection of data or metadata within a multitenant architecture.

Pluggable Databases: These are a movable collection of schemas, schema objects and non-schema objects.

Complete Chapter List

Search this Book:
Reset