Database Server Messaging via SQL Statements

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing messaging systems lack efficient mechanisms for publishing messages from database clients to message brokers without requiring external application layers, and they often fail to provide secure and scalable solutions for authenticating and configuring message broker destinations.

Innovation Solution

The implementation of a broker-based messaging system using Structured Query Language (SQL) allows database servers to receive, process, and publish messages to message brokers, including authentication and configuration settings, entirely within the database server, using SQL statements and stored credentials, without needing external application layers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If messages are published from database clients to message brokers using external application layers, then messaging functionality can be achieved, but system complexity increases and efficiency decreases

Engineering Contradiction:
Improvemessage publishing efficiencyVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent merges the messaging functionality directly into the database server by implementing a messaging client within the database server itself. This allows the database server to publish messages to message brokers natively through SQL statements, eliminating the need for separate external application layers and thereby reducing system complexity while improving messaging efficiency.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The database server is enhanced with multi-functionality by integrating both data processing and messaging capabilities. The messaging client within the database server enables it to perform both traditional database operations and message publishing to brokers, reducing the need for separate specialized components and simplifying the overall system architecture.

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

2Reliability

If message broker configurations are stored externally, then flexibility is maintained, but security risks increase and authentication becomes more complex

Engineering Contradiction:
Improveauthentication securityVSAvoidconfiguration management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines configuration management and authentication mechanisms within the database server's internal architecture. Message broker configurations and credentials are stored and managed natively within the database server, leveraging existing security infrastructure and eliminating the need for separate external configuration management systems.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The database server performs self-service by managing its own message broker configurations, credentials, and authentication internally. The messaging client within the database server automatically handles connection details, credentials, and security management without requiring external configuration management, thereby improving security while simplifying complexity.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If standard database clients and SQL procedures are used for messaging, then ease of operation is improved, but functionality may be limited

Engineering Contradiction:
Improvemessaging operation simplicityVSAvoidmessaging functionality versatility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent enhances the universality of standard database clients by extending their functionality through integrated messaging capabilities. The messaging client within the database server allows standard SQL statements to perform both data operations and message publishing, enabling existing database clients to seamlessly handle diverse messaging scenarios without requiring specialized tools or procedures.

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

Data Source

PatentUS10762180B2Broker-based messaging through SQL
Publication Date: 2020.09.01 SAP SE
  • US10762180B2 patent drawing
  • US10762180B2 patent drawing
  • US10762180B2 patent drawing

AI summary

The disclosure generally describes methods, software, and systems, including a method for publishing messages through a messaging client of a database server. A message to be published to one or more message brokers is received at a server and from a database client. The message is in the form of a SQL statement. The received message is processed at the server. Message broker configurations associated with the received message are determined. The message is published to the one or more message brokers by invoking a messaging client at the server and using at least the message broker configurations.