johnph / simple-transaction Goto Github PK

What about upgrading to latest .NET Core release?

I'm trying to start a new project, found this, and began to smile since is so well documented and feels so right. 🥇

Hello,
Thank you for this great example. I wanted to ask a question about concurrency, for what I have seen, you are using the optimistic concurrency. But on a production server, would this be suitable? Especially for an account that accepts thousands and maybe millions of transactions per day (a big store for example) a lot of transactions would still fail after retrying.

My question to you is how would you handle concurrency on a production server ?

Thanks in advance

EDIT : Hello, I received your comment by email notification but I cannot see it here, I guess you deleted it. Thank you for you quick answer anyway <3 .
Playing around with the code, this version still doesn't handle if they are 2 concurrent withdrawal, you are more likely to do a dirty read on GetAccountSummary(), I wanna contribute to the project if it doesn't bother you.

As for the issue, my intent was to know if you would feel confident putting this same example on a highly solicited payment gateway. too many deposits on the same accounts would result in inconsistent data.

Thank you again for your time!

launchSettings.json contains this:
"launchUrl": "api/values",

which resolves to no controller+action.

launchSettings.json contains this:
"launchUrl": "api/values",

which resolves to no controller+action.

i need your help in some folder tha i didint understand it

Am having this exception when Try it out under swagger of GET account/balance:
System.InvalidOperationException: Unable to resolve service for type 'Microsoft.AspNetCore.Http.IHttpContextAccessor' while attempting to activate 'Transaction.WebApi.Services.IdentityService'.

Solution, add this, as it not registered by default anymore:
services.TryAddSingleton<IHttpContextAccessor, HttpContextAccessor>();