Aurora Service Broker for Cloud Foundry AWS RDS Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The Cloud Foundry platform does not natively support AWS RDS services, limiting developers' ability to use efficient AWS RDS formats for increased operational speed and availability of cloud services.

Innovation Solution

Aurora Service Broker is introduced to provision and de-provision Aurora database instances on AWS, acting as an intermediary between the Cloud Foundry platform and AWS services, utilizing a hardware and software arrangement with a Rds Broker, Rds Helper, Credentials, and Service/Plans information modules to facilitate communication and management of AWS RDS services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If Cloud Foundry platform uses native database services, then platform simplicity is maintained, but access to advanced AWS RDS services and improved operational speed is limited

Engineering Contradiction:
Improveaccess to AWS RDS servicesVSAvoidplatform integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a Service Broker as an intermediary component between the Cloud Foundry platform and AWS RDS services. This broker acts as a mediator that translates Cloud Foundry service requests into AWS-specific API calls, enabling access to advanced AWS RDS features without modifying the core Cloud Foundry platform architecture. The broker handles the complexity of AWS integration while maintaining platform simplicity for end users.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If Cloud Foundry platform integrates AWS RDS services through Service Broker, then access to efficient database services is enabled, but system complexity increases

Engineering Contradiction:
Improveoperational speedVSAvoidservice broker architecture
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the integration architecture into distinct functional components within the Service Broker: an authentication module for security, a service catalog module for service discovery, a provisioning module for resource allocation, and a binding module for application connection. This segmentation allows each component to handle specific tasks independently, making the overall complex system more manageable and maintainable while enabling efficient AWS RDS access.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If developers use traditional database services in Cloud Foundry, then platform simplicity is maintained, but scalability and service management capabilities are limited

Engineering Contradiction:
Improveservice management capabilitiesVSAvoidservice provisioning simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The Service Broker implements self-service capabilities by automatically handling service provisioning, authentication, and configuration tasks. When developers request a database service, the broker autonomously authenticates the user, retrieves service credentials from AWS, provisions the necessary resources, and configures connections without requiring manual intervention. This automation simplifies service management while maintaining platform simplicity for end users.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11005734B2Service broker for cloud foundry platform
Publication Date: 2021.05.11 AGARIK SAS
  • US11005734B2 patent drawing
  • US11005734B2 patent drawing

AI summary

Aurora Service broker for Cloud Foundry platform wherein the Aurora Service broker comprise an hardware and software arrangement to form an interface between the Cloud Foundry platform and Amazon Web Service (AWS) allowing the AWS Service available to applications through Cloud Foundry platform.