Abstract: Techniques are described relating to coordinating asynchronous communication among a plurality of client microservices in a managed services domain of a cloud computing environment. An associated computer-implemented method includes receiving at a single request topic queue of a message broker application programming interface (API) at least one message associated with a topic from at least one publisher microservice among the plurality of client microservices. The method further includes identifying an authorization identification parameter included in each of the at least one message. The method further includes publishing each of the at least one message to a respective bucket within a single response topic queue of the message broker API, the respective bucket corresponding to one of at least one subscriber microservice among the plurality of client microservices associated with the authorization identification parameter included in the message.

Abstract: A method, system, and computer program product for workflow-based dynamic screen sharing in a multi-screen presentation environment are provided. The method identifies a presentation schema for a multi-screen presentation. A set of presenters are identified for the multi-screen presentation. The method determines a presentation rate of the multi-screen presentation during the multi-screen presentation. A workflow visualization is generated for the multi-screen presentation based on the presentation schema and the presentation rate. The method dynamically transitions between presenters of the set of presenters during the multi-screen presentation based on the presentation schema, the presentation rate, and the workflow visualization.

Abstract: A method, including: transmitting, by a first circuit to outside a user's body, information related to a first medication ingested by the user, the first circuit being digestible by gastric juices of the user, the first circuit being covered by a first thickness of a first digestible material; and transmitting, by a second circuit to outside the user's body, information related to a second medication ingested by the user, the second circuit being digestible by the gastric juices of the user, the second circuit being covered by a second thickness of a second digestible material and the first thickness of the first digestible material.

Abstract: Techniques are described relating to coordinating asynchronous communication among a plurality of client microservices in a managed services domain of a cloud computing environment. An associated computer-implemented method includes receiving at a single request topic queue of a message broker application programming interface (API) at least one message associated with a topic from at least one publisher microservice among the plurality of client microservices. The method further includes identifying an authorization identification parameter included in each of the at least one message. The method further includes publishing each of the at least one message to a respective bucket within a single response topic queue of the message broker API, the respective bucket corresponding to one of at least one subscriber microservice among the plurality of client microservices associated with the authorization identification parameter included in the message.

Abstract: A method, system, and computer program product for workflow-based dynamic screen sharing in a multi-screen presentation environment are provided. The method identifies a presentation schema for a multi-screen presentation. A set of presenters are identified for the multi-screen presentation. The method determines a presentation rate of the multi-screen presentation during the multi-screen presentation. A workflow visualization is generated for the multi-screen presentation based on the presentation schema and the presentation rate. The method dynamically transitions between presenters of the set of presenters during the multi-screen presentation based on the presentation schema, the presentation rate, and the workflow visualization.

Abstract: A blockchain may be used to store transactions in an immutable ledger. The types of transactions may vary and the information from the transactions could be used to identify information about nodes in a particular network. One example operation may include one or more of identifying a number of nodes operating on a blockchain, determining a new blockchain transaction, and determining one or more of the nodes as having one or more characteristics based on the new blockchain transaction.

Abstract: Embodiments include a computer-implemented method including identifying, by a primary computer device, a plurality of records, each record having one or more attributes; standardizing, by the primary computer device, each of the plurality of records; assigning, by the primary computer device, an index to one or more of the one or more attributes; providing, by the primary computer device, instructions for clustering the standardized plurality of records in parallel into one or more clusters, each cluster including records having the same index, the one or more clusters being in a group; receiving, by the primary computer device, one or more groups, each group including one or more clusters sharing a same index; and linking one or more of the plurality of records in a cluster with another one or more of the plurality of records in another cluster within a same group.

Abstract: A system and method for intelligent visualization of unstructured data in a column-oriented data table includes receiving unstructured data from a plurality of sources for recording into the column-oriented data table having a database schema using a plurality of keys to visualize one or more attributes in the column-oriented data table, determining that a semantically related key is used to visualize the one or more attributes contained in the unstructured data received from the plurality of sources, wherein the semantically related key is different from the plurality of keys and is not synchronized with the database schema of the column-oriented data table, formatting the unstructured data to synchronize the unstructured data with the database schema of the column-oriented data table, and outputting the synchronized unstructured data into the column-oriented data table so that the unstructured data is visualized according to the database schema of the column-oriented data table.

Abstract: A first entity and a second entity can be retrieved from a database and compared. The first entity and the second entity can each comprise at least one respective primary key, at least one respective attribute, and at least one pair of corresponding instances. One or more equivalent attributes can be identified, and, for each equivalent attribute, a set of attribute value differences can be compiled for each respective corresponding instance between the first entity and the second entity.

Abstract: Embodiments include a computer-implemented method including identifying, by a primary computer device, a plurality of records, each record having one or more attributes; standardizing, by the primary computer device, each of the plurality of records; assigning, by the primary computer device, an index to one or more of the one or more attributes; providing, by the primary computer device, instructions for clustering the standardized plurality of records in parallel into one or more clusters, each cluster including records having the same index, the one or more clusters being in a group; receiving, by the primary computer device, one or more groups, each group including one or more clusters sharing a same index; and linking one or more of the plurality of records in a cluster with another one or more of the plurality of records in another cluster within a same group.

Abstract: A system and method for intelligent visualization of unstructured data in a column-oriented data table includes receiving unstructured data from a plurality of sources for recording into the column-oriented data table having a database schema using a plurality of keys to visualize one or more attributes in the column-oriented data table, determining that a semantically related key is used to visualize the one or more attributes contained in the unstructured data received from the plurality of sources, wherein the semantically related key is different from the plurality of keys and is not synchronized with the database schema of the column-oriented data table, formatting the unstructured data to synchronize the unstructured data with the database schema of the column-oriented data table, and outputting the synchronized unstructured data into the column-oriented data table so that the unstructured data is visualized according to the database schema of the column-oriented data table.

Abstract: A blockchain may be used to store transactions in an immutable ledger. The types of transactions may vary and the information from the transactions could be used to identify information about nodes in a particular network. One example operation may include one or more of identifying a number of nodes operating on a blockchain, determining a new blockchain transaction, and determining one or more of the nodes as having one or more characteristics based on the new blockchain transaction.

Abstract: A blockchain may be used to store transactions in an immutable ledger. The types of transactions may vary and the information from the transactions could be used to identify information about nodes in a particular network. One example operation may include one or more of identifying a number of nodes operating on a blockchain, determining a new blockchain transaction, and determining one or more of the nodes as having one or more characteristics based on the new blockchain transaction.

Abstract: A first entity and a second entity can be retrieved from a database and compared. The first entity and the second entity can each comprise at least one respective primary key, at least one respective attribute, and at least one pair of corresponding instances. One or more equivalent attributes can be identified, and, for each equivalent attribute, a set of attribute value differences can be compiled for each respective corresponding instance between the first entity and the second entity.

Abstract: A first entity and a second entity can be retrieved from a database and compared. The first entity and the second entity can each comprise at least one respective primary key, at least one respective attribute, and at least one pair of corresponding instances. One or more equivalent attributes can be identified, and, for each equivalent attribute, a set of attribute value differences can be compiled for each respective corresponding instance between the first entity and the second entity.

Abstract: A blockchain may be used to store transactions in an immutable ledger. The types of transactions may vary and the information from the transactions could be used to identify information about nodes in a particular network. One example operation may include one or more of identifying a number of nodes operating on a blockchain, determining a new blockchain transaction, and determining one or more of the nodes as having one or more characteristics based on the new blockchain transaction.

Abstract: A first entity and a second entity can be retrieved from a database and compared. The first entity and the second entity can each comprise at least one respective primary key, at least one respective attribute, and at least one pair of corresponding instances. One or more equivalent attributes can be identified, and, for each equivalent attribute, a set of attribute value differences can be compiled for each respective corresponding instance between the first entity and the second entity.

Abstract: Flexibly modeling and visualizing a level-based hierarchy. A first level set and a second level set are identified from a first data set and a second data set in a first domain and a second domain, respectively. A first relationship type to be used between the first level set and the second level set is received. A first hierarchy is formalized, including at least the first level set and the second level set joined in a hierarchical relationship according to the first relationship type.

Abstract: Flexibly modeling and visualizing a level-based hierarchy. A first level set and a second level set are identified from a first data set and a second data set in a first domain and a second domain, respectively. A first relationship type to be used between the first level set and the second level set is received. A first hierarchy is formalized, including at least the first level set and the second level set joined in a hierarchical relationship according to the first relationship type.