# US 2020/0396306 A1 · Apparatuses and methods for a distributed message service in a virtualized computing system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0396306 A1
- Document ID: US20200396306A1
- Status: Published application
- Kind: A1
- Application number: 16/528,006
- Filed: 2019-07-31
- Published: 2020-12-17
- Earliest claimed: 2019-06-13
- Assignees: Nutanix, Inc.
- Applicants: Nutanix, Inc.
- Inventors: AMOD VILAS JALTADE; ADITYA VILAS JALTADE; CHINMAY DINESH KAMAT; GOWTHAM ALLURI; HARSHIT AGARWAL; KARAN GUPTA; MAYUR VIJAY SADAVARTE; MONIL DEVANG SHAH; PARTHA RAMACHANDRAN; RAMYA BOLLA
- Web page: https://patentgrep.com/patent/US20200396306A1

## CPC

- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- H04L 67/562: Brokering proxy services
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)}
- G06F 9/546: {Message passing systems or structures, e.g. queues}
- G06F 16/182: Distributed file systems
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- G06F 2009/4557: {Distribution of virtual machine instances; Migration and load balancing}
- G06F 2009/45579: {I/O management, e.g. providing access to device drivers or storage}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Examples of a distributed message service include a virtualized file system including a virtual disk configured to store messages for a message topic, and a broker logically allocated to the message topic. The broker is configured to cause a message directed to the message topic provided from a publisher to be stored at the virtual disk, and to route the message to a subscriber of the message topic that is registered with the broker. The distributed message service further includes an operating system configured to manage the virtualized file system and includes a message service configured to manage logical allocation of the broker and manage allocation of the virtual disk to the message topic.

## Claims

### Claim 1

At least one non-transitory computer-readable storage medium including instructions that when executed by a computing node of a computing node cluster, causes the computing node to:
receive, from a publisher, a first message directed to a first partition of a message topic at a first message service;
store, via a first broker of the message service that is logically allocated to the first partition of the message topic, the first message at a first partition of a virtual disk of a virtualized file system hosted on the computing node cluster;
receive, from the publisher, a second message directed to a second partition of the message topic at the message service;
store, via a second broker of the message service that is logically allocated to the second partition of the message topic, the second message at a second partition of the virtual disk; and
in response to failure of the first broker of the message service, instantiate a new first broker of the message service that is logically allocated to the first partition of the message topic.

### Claim 2

(canceled)

### Claim 3 (depends on 1)

The at least one non-transitory computer-readable storage medium of claim 1, further including instructions which cause the computing node to append the first message to the first partition of the virtual disk to store the first message.

### Claim 4 (depends on 1)

The at least one non-transitory computer-readable storage medium of claim 1, further including instructions to route, via the first broker and the second broker, the first message and the second message, respectively, to a subscriber.

### Claim 5 (depends on 1)

The at least one non-transitory computer-readable storage medium of claim 1 further including instructions to route the first message to a subscriber in response to the subscriber being included in a subscriber list corresponding to the message topic.

### Claim 6 (depends on 5)

The at least one non-transitory computer-readable storage medium of claim 5, further including instructions to add the subscriber to the subscriber list in response to receipt of a request from the subscriber.

### Claim 7 (depends on 1)

The at least one non-transitory computer-readable storage medium of claim 1, further including instructions to convert the first message from a first application programming interface (API) type to a second API type prior to storing the first message at the first partition of the virtual disk.

### Claim 8 (depends on 1)

The at least one non-transitory computer-readable storage medium of claim 1, further including instructions to increase a size of the virtual disk in response to available storage being less than an available storage threshold.

### Claim 9 (depends on 1)

The at least one non-transitory computer-readable storage medium of claim 1, further including instructions which cause the computing node to logically allocate a third broker of the message service to a partition of a second topic in response to receiving a registration request from the third broker.

### Claim 10 (depends on 1)

The at least one non-transitory computer-readable storage medium of claim 1, further including instructions to manage a lifecycle of the first broker using a containerized architecture.

### Claim 11

A computing node cluster, comprising one or more processors and memory configured to cause the computing node cluster to host:
a virtualized file system including a virtual disk configured to store messages for a message topic;
a broker logically allocated to the message topic, wherein the broker is configured to cause a message directed to the message topic provided from a publisher to be stored at the virtual disk, wherein the broker is further configured to route the message to a subscriber of the message topic that is registered with the broker; and
an operating system configured to manage the virtualized file system, the operating system including a message service configured to manage logical allocation of the broker and manage allocation of the virtual disk to the message topic, wherein, in response to failure of the broker, the operating system is configured to instantiate a new broker that is logically allocated to the message topic.

### Claim 12

(canceled)

### Claim 13 (depends on 10)

The computing node cluster of claim 10, wherein the new broker is configured to cause a second message directed to the message topic provided from the publisher to be stored at the virtual disk.

### Claim 14 (depends on 11)

The computing node cluster of claim 11, wherein the broker is configured to append the message to the virtual disk.

### Claim 15 (depends on 11)

The computing node cluster of claim 11, wherein the broker is configured to provide the message to a subscriber in response to the subscriber being included in a subscriber list corresponding to the message topic.

### Claim 16 (depends on 15)

The computing node cluster of claim 15, wherein the message service is configured to add the subscriber to the subscriber list in response to receipt of a request from the subscriber.

### Claim 17 (depends on 11)

The computing node cluster of claim 11, wherein the broker is configured to convert the message from a first application programming interface (API) type to a second API type prior to storing the message at the virtual disk.

### Claim 18 (depends on 11)

The computing node cluster of claim 11, wherein the message service is configured to increase a size of the virtual disk in response to available storage being less than an available storage threshold.

### Claim 19 (depends on 11)

The computing node cluster of claim 11, wherein the message service is configured to logically allocate the broker to a first partition of the message topic and a second broker to a second partition of the message topic in response to receiving a registration request from the second broker.

### Claim 20 (depends on 11)

The computing node cluster of claim 11, wherein the message service is configured to instantiate the broker using a containerized architecture.

### Claim 21

A method, comprising:
receiving, from a publisher, a first message directed to a first partition of a message topic at a first message service hosted on a first computing node of a computing node cluster;
storing, via a broker of the first message service that is logically allocated to the first partition of the message topic, the first message at a first partition of a virtual disk of a virtualized file system hosted on the computing node cluster;
receiving, from the publisher, a second message directed to a second partition of the message topic at a second message service hosted on a second computing node of the computing node cluster; and
storing, via a broker of the second message service that is logically allocated to the second partition of the message topic, the second message at a second partition of the virtual disk; and
in response to failure of the broker of the first message, instantiating a new broker of the first message service that is logically allocated to the first partition of the message topic.

### Claim 22

(canceled)

### Claim 23 (depends on 21)

The method of claim 21, further comprising routing, via the broker of the first message service and the broker of the second message service, the first message and the second message, respectively, to a subscriber in response to the subscriber being included in a subscriber list corresponding to the message topic.

### Claim 24 (depends on 21)

The method of claim 21, further comprising converting the first message from a first application programming interface (API) type to a second API type prior to storing the first message at the first partition of the virtual disk.

### Claim 25 (depends on 21)

The method of claim 21., further comprising managing a lifecycle of the broker of the first message service using a containerized architecture.

### Claim 26 (depends on 21)

The method of claim 21, further including increasing a size of the virtual disk in response to available storage being less than an available storage threshold.

### Claim 27 (depends on 1)

The at least one non-transitory computer-readable storage medium of claim 1, further including instructions to resume storage of subsequent messages directed to the first partition of the message topic to the first partition of the virtual disk where the first broker left off via the new first broker.

### Claim 28 (depends on 21)

The method of claim 21, further comprising resuming storage of subsequent messages directed to the first partition of the message topic to the first partition of the virtual disk where the first broker left off via the new first broker.
