Simplify application development with Oracle Real Application Clusters
summary
Oracle RAC claims to remove most failure-detection and retry code by routing clients through a SCAN (Single Client Access Name) and service-based connect strings, keeping connection pools updated via LREG and automatic load/failure notifications. Built features include session failover with state replay using -failover_restore AUTO, rolling maintenance with configurable drain timeouts, and Zero downtime GI patching (plus ksplice on Exadata). Applications run unchanged across on‑prem, Exadata, cloud and Autonomous Database while adding horizontal scaling and high availability.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:30Choose the right database for your applications
- 1:24Oracle Real Application Clusters (RAC) Fullik al application development requirements
- 3:33Connect using user-defined service name
- 5:51Services enable load balancing and protect against failures
- 9:07How does Oracle RAC simplify failure detection for applications? Comprehensive failure detection, resolution, and notification
- 12:15Oracle RAC keeps applications available during maintenance
- 16:06Oracle RAC keeps applications available during outages
- 20:14Delegate failure handling to Oracle RAC
- 21:05Seamless high availability and scalability regardless of Adjust connect string to port applications between deployments
- 21:36deployment choice
- 22:53Oracle RAC improves developer productivity Application developers focus on writing business logic
related talks
29mFuture-proof your applications using RAC
24mHigh Availability and Disaster Recovery Smart Features
34mUnder the covers of Oracle Real Application Cluster deployments
16mOracle MAA for Data Resiliency Across Hyperscalers
26mOracle Database Appliance overview and best practices
32mActive Data Guard: Disaster recovery tips and tricks
31mAutonomous Database: Simplify your database management
30mCloud native low code apps with Oracle APEX on Oracle Autonomous Database