BRANCH-BASED RECOVERY IN A DATABASE SYSTEM

    公开(公告)号:US20210064601A1

    公开(公告)日:2021-03-04

    申请号:US16552119

    申请日:2019-08-27

    Abstract: A staging table created in a database system may store a snapshot of live database table captured prior to an unintended change to the live database table. One or more entries in the staging table may be updated to incorporate one or more intended changes to the live database table that occurred after the unintended change. The live database table may be updated by merging each of the updated entries from the staging table to the live database table. The updated database table may eliminate the unintended change.

    PARTITION BALANCING IN AN ON-DEMAND SERVICES ENVIRONMENT

    公开(公告)号:US20190312926A1

    公开(公告)日:2019-10-10

    申请号:US16450920

    申请日:2019-06-24

    Abstract: Techniques for partition balancing. Organization identifiers (orgIDs) are acquired for one or more organizations within a multi-organization on-demand services environment having multiple nodes, each of which have one or more partitions. A mapping of the orgIDs to the partitions within the multi-organization on-demand services environment is determined. Resource consumption for the organizations is determined. Resource consumption for the partitions based on the resource consumption of the organization and the mapping of the organization to the partitions is determined. A score for the partitions based on the resource consumption is generated. The partitions are redistributed among the nodes based on the partition scores.

    Systems and methods for implementing bulk handling in asynchronous processing

    公开(公告)号:US10019297B2

    公开(公告)日:2018-07-10

    申请号:US14306113

    申请日:2014-06-16

    CPC classification number: G06F9/546 G06F16/2455 G06F2209/548 H04L67/26

    Abstract: Systems and methods for implementing bulk handling in asynchronous processing are described. For example, an exemplary system includes a processor and a memory to execute instructions at the system; a broker to enqueue received messages; a push connection from the broker to a thread, in which the broker is to push an initial message to the thread for processing; a pull connection from the thread to the broker, in which the thread is to request one or more additional messages for bulk processing with the initial message from the broker; a query interface to issue a database query from the thread to a data store, the database query specifying the initial message and the one or more additional messages as a set of messages to obtain a lock for the set of messages; and a message processing engine to handle the set of messages in bulk based on whether the lock for the set of messages is obtained.

    SYSTEMS AND METHODS FOR SUPPORTING TRANSACTIONAL MESSAGE HANDLING
    28.
    发明申请
    SYSTEMS AND METHODS FOR SUPPORTING TRANSACTIONAL MESSAGE HANDLING 有权
    支持交易信息处理的系统和方法

    公开(公告)号:US20150081645A1

    公开(公告)日:2015-03-19

    申请号:US14488159

    申请日:2014-09-16

    CPC classification number: G06F11/1446 G06F9/466 G06F17/30362

    Abstract: In accordance with embodiments disclosed herein, there are provided methods, systems, and apparatuses including, for supporting transactional message handling in an on-demand service environment including, for example: enqueuing a message specifying a transaction to be processed via a host organization; inserting a row into a database of the host organization associating the message with a status of pending, wherein the row is autocommitted to the database upon insertion; updating the status for the row to ready if a commit operation for the transaction is initiated; requesting a lock on the row; and performing final processing for the transaction based on the status for the message and based further on whether the lock is obtained for the row. Final processing may include, for example, a transaction roll back, a transaction commit, a transaction requeue, a termination of transaction processing, or an orphaned transaction clean up.

    Abstract translation: 根据本文公开的实施例,提供了包括用于在按需服务环境中支持事务性消息处理的方法,系统和装置,包括例如:排队指定要经由主机组织处理的事务的消息; 将一行插入主机组织的数据库中,将该消息与待处理状态相关联,其中该行在插入时自动提交到数据库; 如果事务的提交操作被启动,则将该行的状态更新为就绪; 请求在行上锁; 并且基于消息的状态对事务执行最终处理,并且还基于是否为该行获得锁定。 最终处理可以包括例如事务回滚,事务提交,事务重新排序,事务处理的终止或孤立的事务清理。

    Cloud services release orchestration

    公开(公告)号:US11748090B2

    公开(公告)日:2023-09-05

    申请号:US18049265

    申请日:2022-10-24

    CPC classification number: G06F8/65

    Abstract: According to some implementations, while a proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (cos) pods having first app version containers, configuration information is received including an identification of a second app version container image for a second app version. The second app version is an updated version of the first app version. Cos pods having second app version containers are brought up based on the second app version container image identified in the configuration information. Test and/or warmup traffic is caused to be routed to the second app version containers. Responsive to an indication regarding the routing of the test and/or warmup traffic to the second app version, causing a transition to sending production traffic to the second app version containers instead of to the first app version.

    Cloud services release orchestration with a reusable deployment pipeline

    公开(公告)号:US11507364B2

    公开(公告)日:2022-11-22

    申请号:US17225143

    申请日:2021-04-08

    Abstract: Cloud services release orchestration with a reusable deployment pipeline. According to some implementations, responsive to receiving from a COS controller parameters from configuration information provided to the COS controller while an app aware proxy routes production traffic to a first application (app) version that communicates with a database management system (DBMS) and that runs in container orchestration system (COS) pods having first app version containers, causing a validation of a second app version using COS pods having second app version containers that are now live after having been brought up by the COS controller responsive to the provision of the configuration information. After the validation, causing the transition to sending production traffic to the second app version containers that are determined to be live instead of to the first app version containers. Then causing post-release activities using DBMS connection information for the first app version that was in the configuration information and that was provided through the COS controller.

Patent Agency Ranking