Transaction coordination across services

A computer-implemented system comprising:

• a storage comprising transaction state data;
• and
• a processor that receives, with a service running on the processor, a transaction that is part of a multi-part transaction, wherein the service comprises virtual threads,
• determines, with the service running on the processor using any of the virtual threads of the service, the transaction does not already exist in the transaction state data for the service,
• updates, with the service running on the processor using any of the virtual threads of the service, the status of the transaction in the transaction state data for the service to pending,
• processes, with the service running on the processor using any of the virtual threads of the service, the transaction,
• updates, with the service running on the processor using any of the virtual threads of the service, the status of the transaction in the transaction state data for the service to completed,
• receives, with the service running on the processor at an endpoint of the service, a request for the status of the transaction,
• responds, with the service running on the processor using any of the virtual threads of the service, to the request for the status of the transaction,
• sends, with the service running on the processor using any of the virtual threads, a request for status to an endpoint of at least one other service that is processing at least one other transaction of the multi-part transaction, and
• receives, with the service running on the processor using at any of the virtual threads, a response from the at least one other service of a status of completed.

A system comprising:

• one or more computers and one or more non-transitory storage devices storing instructions which are operable, when executed by the one or more computers, to cause the one or more computers to perform operations comprising:
• receiving, using a service running on a processor, a transaction that is part of a multi-part transaction, wherein the service comprises virtual threads spawned by the service and running on the processor;
• determining, using the service using any of the virtual threads of the service, the transaction does not already exist in transaction state data for the service;
• updating, using the service using any of the virtual threads of the service, the status of the transaction in the transaction state data for the service to pending;
• processing, using the service using any of the virtual threads of the service, the transaction;
• updating, using the service using any of the virtual threads of the service, the status of the transaction in the transaction state data for the service to completed;
• receiving, using the service at an endpoint of the service, a request for the status of the transaction;
• responding, using the service using any of the virtual threads of the service, to the request for the status of the transaction;
• sending, using the service using any of the virtual threads of the service, a request for status to an endpoint of at least one other service that is processing at least one other transaction of the multi-part transaction;
• and
• receiving, using the service using at any of the virtual threads, a response from the at least one other service of a status of completed.