Backend as a Service for Declarative Database Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developing applications requires significant time and resources due to the complexity of configuring new applications with external services and databases, particularly in integrating third-party services and managing data access, which often necessitates writing extensive boilerplate backend code.

Innovation Solution

The system provides a backend as a service that allows developers to interact with databases and services using declarative statements, reducing the need for traditional backend architecture and enabling direct database access from client applications while ensuring security and access control through a REST-compliant API, thus simplifying the integration of third-party services and data management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional backend architecture is used to integrate third-party services and manage database access, then security and access control can be implemented, but development time and complexity increase significantly

Engineering Contradiction:
Improvesecurity and access controlVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces a backend-as-a-service layer that acts as an intermediary between client applications and external services/databases. This service handles authentication, authorization, and data access control centrally, eliminating the need for each application to implement its own backend security logic. The intermediary service manages complex security requirements while allowing developers to focus on frontend functionality, thus resolving the contradiction between maintaining security and reducing development time.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If extensive backend code is written to connect applications with databases and services, then data access and service integration are achieved, but the quantity of code and complexity increase

Engineering Contradiction:
Improveservice integration capabilityVSAvoidbackend code complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal backend-as-a-service that provides multi-functional capabilities including database access, third-party service integration, authentication, and data management through a unified interface. This single service handles multiple functions that would otherwise require separate backend implementations for each application, reducing code complexity while maintaining adaptability to integrate with various services and databases.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent segments the backend functionality into a separate, reusable service layer that can be independently configured and managed. By dividing the backend concerns from the application logic, the system reduces complexity in individual applications while maintaining comprehensive service integration capabilities through the modular backend service.

Inventive Principle:
Principle #1Segmentation

3Productivity

If developers focus on frontend code with backend as a service, then productivity increases, but direct database access control becomes more challenging

Engineering Contradiction:
Improvedeveloper productivityVSAvoiddatabase access control
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The backend-as-a-service automatically handles database access control, authentication, and authorization without requiring developers to manually implement these features. The service provides self-service capabilities where access control policies are managed centrally, and the system automatically enforces security rules for database operations initiated from frontend applications, thus maintaining ease of operation while enabling high productivity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11630642B2Systems and methods for managing a database back end as a service
Publication Date: 2023.04.18 MONGODB INC
  • US11630642B2 patent drawing
  • US11630642B2 patent drawing
  • US11630642B2 patent drawing

AI summary

Systems and methods for managing a database back end as a service are described. In some aspects, the described systems and methods provide for a cloud-based resource for servicing a request for data from an application to a remote database and/or a service. In some aspects, the described systems and methods provide for a cloud-based application client for requesting data from a remote database and/or a service.