Abstract: Certain aspects of the present disclosure provide techniques for processing north-south queries in an application programming interface (API) generated for a plurality of associated services. The method generally includes receiving a request to invoke a function exposed by a first service in the API, wherein the function commits data to one or more data repositories. A data record is generated by the first service based on the received request based on a data object definition and a service definition for the first service. A message is generated including the generated data record and an indication that the message is to be consumed by a data lake processing system to commit data to a data lake. The message is published on a message bus for consumption by the data lake processing system.

Abstract: Certain aspects of the present disclosure provide techniques for processing east-west queries in an application programming interface (API) generated for a plurality of associated services. The method generally includes receiving, at a request gateway from a requesting service, a request to invoke a function exposed by a first service through the API. References to entities defined in a declarative schema for one or more second services are identified based on identifiers included a record retrieved from a data repository for an entity returned by the function. A message is published on a message bus to the one or more second services to retrieve information related to the referenced entities. A response message including objects associated with the referenced entities is consumed. The function is executed based on the objects associated with the referenced entities, and the result generated by executing the function is returned to the requesting service.

Abstract: Certain aspects of the present disclosure provide techniques for processing north-south queries in an application programming interface (API) generated for a plurality of associated services. The method generally includes receiving a request to invoke a function exposed by a first service in the API, wherein the function commits data to one or more data repositories. A data record is generated by the first service based on the received request based on a data object definition and a service definition for the first service. A message is generated including the generated data record and an indication that the message is to be consumed by a data lake processing system to commit data to a data lake. The message is published on a message bus for consumption by the data lake processing system.

Abstract: Certain aspects of the present disclosure provide techniques for processing east-west queries in an application programming interface (API) generated for a plurality of associated services. The method generally includes receiving, at a request gateway from a requesting service, a request to invoke a function exposed by a first service through the API. References to entities defined in a declarative schema for one or more second services are identified based on identifiers included a record retrieved from a data repository for an entity returned by the function. A message is published on a message bus to the one or more second services to retrieve information related to the referenced entities. A response message including objects associated with the referenced entities is consumed. The function is executed based on the objects associated with the referenced entities, and the result generated by executing the function is returned to the requesting service.

Abstract: Certain aspects of the present disclosure provide techniques for generating an application programming interface (API) for a plurality of associated services. The method generally includes retrieving a declarative schema for a service of a plurality of services in an application programming interface (API). A language object for the service is generated from a data object definition in the declarative schema associated with the service. Generally, the language object is configured to handle data events generated by the service. A service controller for the service is generated from a service definition in the declarative schema associated with the respective service. Generally, the service controller is fronted by a gateway for external sources to invoke one or more functions implemented by the service. An application programming interface (API) is exposed for the service independently of details of APIs for the associated services to one or more external services.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store configured to receive, from a first entity, a request to push a detailed transaction corresponding to a secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The data store may be further configured to store the detailed transaction based on a first determination to trust the first entity. The system may further include an access controller configured to perform the first determination by applying a first security rule corresponding to a type of the secure identifier to the request to push the detailed transaction, and a registry configured to store at least the first security rule.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store and a registry configured to receive a request to register a universal resource identifier (URI) to a data store with a first secure identifier. The first secure identifier may be generated, using an encoding function and by a user, from a user identifier of the user. The registry may be further configured to store the URI of the data store with the first secure identifier, and receive, from an entity, a request to lookup a data store registered with a second secure identifier. The second secure identifier may be generated by the entity. The registry may be further configured to retrieve the URI of the data store in response to the request to lookup the data store, and transmit, to the entity, the URI of the data store.

Abstract: Certain aspects of the present disclosure provide techniques for generating an application programming interface (API) for a plurality of associated services. The method generally includes retrieving a declarative schema for a service of a plurality of services in an application programming interface (API). A language object for the service is generated from a data object definition in the declarative schema associated with the service. Generally, the language object is configured to handle data events generated by the service. A service controller for the service is generated from a service definition in the declarative schema associated with the respective service. Generally, the service controller is fronted by a gateway for external sources to invoke one or more functions implemented by the service. An application programming interface (API) is exposed for the service independently of details of APIs for the associated services to one or more external services.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store configured to receive, from a first entity, a request to push a detailed transaction corresponding to a secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The detailed transaction may identify at least one selected from a group consisting of products and services received by the user from the first entity. The data store may be further configured to store the detailed transaction based on a first determination to trust the first entity. The system may further include an access controller configured to perform the first determination by applying a first security rule corresponding to a type of the secure identifier to the request to push the detailed transaction, and a registry configured to store at least the first security rule.

Abstract: A method for the automated time tracking of events in a calendar and the use of the same to generate invoices, which includes detecting an event record creation request received from a user, monitoring, based on the event record creation request, user input including event details for an event record, identifying a control character within the user input, while monitoring the user input, populating, in response to identifying the control character, a list comprising one or more contacts from a contact group of the user, displaying, to the user, the list of the one or more contacts, receiving a selection of a contact from within the list, and inserting an identifier of the contact within the event record, based on the selection.

Abstract: A method, system, and computer readable medium to process transaction records obtained from electronic commerce applications (ECAs) as staged transactions before posting to an accounting ledger in a financial management application (FMA). In this manner, the user (e.g., small business owner, book keeper, or accountant), the ECA developer, and the FMA provider are allowed to focus on their respective domain knowledge while allowing the financial management application, augmented by user-defined rules that are appropriate to the business in question, to automate the accounting ledger posting.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store configured to receive, from a first entity, a request to push a detailed transaction corresponding to a secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The data store may be further configured to store the detailed transaction based on a first determination to trust the first entity. The system may further include an access controller configured to perform the first determination by applying a first security rule corresponding to a type of the secure identifier to the request to push the detailed transaction, and a registry configured to store at least the first security rule.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store configured to receive, from a first entity, a request to push a detailed transaction corresponding to a secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The detailed transaction may identify at least one selected from a group consisting of products and services received by the user from the first entity. The data store may be further configured to store the detailed transaction based on a first determination to trust the first entity. The system may further include an access controller configured to perform the first determination by applying a first security rule corresponding to a type of the secure identifier to the request to push the detailed transaction, and a registry configured to store at least the first security rule.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store and a registry configured to receive a request to register a universal resource identifier (URI) to a data store with a first secure identifier. The first secure identifier may be generated, using an encoding function and by a user, from a user identifier of the user. The registry may be further configured to store the URI of the data store with the first secure identifier, and receive, from an entity, a request to lookup a data store registered with a second secure identifier. The second secure identifier may be generated by the entity. The registry may be further configured to retrieve the URI of the data store in response to the request to lookup the data store, and transmit, to the entity, the URI of the data store.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store configured to receive, from a first entity, a request to push a detailed transaction corresponding to a secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The data store may be further configured to store the detailed transaction based on a first determination to trust the first entity. The system may further include an access controller configured to perform the first determination by applying a first security rule corresponding to a type of the secure identifier to the request to push the detailed transaction, and a registry configured to store at least the first security rule.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store. The system may further include a registry configured to receive, from a user, a first secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The registry may be further configured to receive a first selection of a first data store of a first transaction storage device, and store a first registration of the first data store with the first secure identifier. The first registration may include a universal resource identifier (URI) of the first data store. The registry may be further configured to receive, from a service provider, a first request to lookup a data store registered with the first secure identifier, retrieve the first registration, and transmit, to the service provider and using the first registration, the URI of the first data store.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store configured to receive a request, from a service provider, to push a detailed transaction corresponding to a secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The data store may be further configured to store the detailed transaction based on a determination that the detailed transaction is valid. The system may further include a validator configured to obtain, from a registry, a validation rule corresponding to the secure identifier, and perform the determination. The determination may include applying the validation rule to the request. The system may further include the registry. The registry may be configured to store at least the validation rule.