Features: Idempotency

Mon, 01 Jan 0001 00:00:00 +0000

The idempotency strategy is widely applied to avoid, for example, the collection of a duplicate payment received in the API. To better visualize, we are talking about the request with a POST/PUT/PATCH command or an event that arrives duplicated by the Stream.

Some Stream services sometimes send duplicate messages to ensure high delivery speed, and this forces applications to control idempotency.

Devprime offers a very flexible approach to service configuration that can be configured to start automatically, per parameter sent by the consumer, and/or restricted to specific processes according to each microservice’s strategy.

The idempotency feature can be configured to work automatically using the “action” parameter as “auto” and the “flow” parameter as “backend” enabling the feature without the need to pass a foreign key when consuming the API.

To better visualize the scenario in practice, it is essential to follow the sequence of images where we demonstrate the entire process in the Log. Auto-Logging is generated by the native Servability approach.

Making the First Post to the Orders API
When you examine the log, view the idempotency information as active in that request, initiating duplicate protection.

Make a second post in the Requests API identical to the previous one
Right now we are repeating the scenario, only now we will have another answer in the control of idempotency.

When analyzing the API result, we see the duplicate request decline

When you look at the Log in the idempotency section you will find the “Reject”

Two-step configuration of idempotency
Setup is a simple and customizable process

Enable Idempotency on the “Devprime_App” key by setting the “Enable” value to “true”.

    "Idempotency": {
      "Enable": "true",
      "Alias": "State2",
      "Duration": "86400",
      "Flow": "backend",
      "key": "idempotency-key",
      "Scope": "all",
      "Action": "auto"
    }

Add a second Redis persistence in the “State” key for idempotency automatic transaction control information.

{
  "enable": "true",
  "alias": "State2",
  "dbtype": "redis",
  "connection": "127.0.0.1:6379,password=LltF8Nx*yo",
  "timeout": "5",
  "retry": "2",
  "durationofbreak": "45"
}

Activating idempower manually
In the desired scenarios, you can manually configure idempotency support.

app.MapPost("/v1/order", async (HttpContext http,
IOrderService Service, 
Devprime.Web.ViewModels.Order.Order command) =>
await Dp(http).Pipeline(() =>
        {
            Dp(http).Idempotency.Enable = true;
            Service.Add(command.ToApplication());
        }));

You’ve just checked out a powerful feature present in Devprime Stack. Use the Devprime platform to accelerate the journey of application modernization and digital platform development.

More details on deidempotency scenarios
Implementing idempotency in microservices
Idepotency in microservices and REST APIs
Implementing idempotency in microservices

Features: Local Transaction

Mon, 01 Jan 0001 00:00:00 +0000

By enabling this functionality, operations in the database are isolated in an automatic transactional context and only in case of success is the transaction confirmed.

The transactional context can be initialized at the business scope within the domain by adding the “ExecuteTransaction” in the Devprime pipeline or directly at the database store scope with the “ExecuteTransaction” or “ExecuteTransactionResult” command as per the desired scenario in the operation.

Including the transactional context in the “Aggregate Root” domain
Including the transactional context in the “Database” repository

Features: Distributed transaction

Mon, 01 Jan 0001 00:00:00 +0000

Devprime | Documentation – Distributed Systems

Features: Idempotency

Features: Local Transaction

Features: Distributed transaction