Can you estimate what proportion of fraud is automated/bot/scripted versus manual human interaction? Do you rely much on botnet detection or IP reputation?
Card testing doesn’t require a purchase, fraudsters can validate a card by adding it to an online wallet. The retailer will send a $0 authorization to the bank.
Fraud happens across all transaction amounts, what do you think people use the cards for once they buy or guess a valid card?
Call it Blazor weirdness then. This obviously wasn’t a swipe at Microsoft being closed, just a point that Blazor stuff is not general standard web stuff.
People are conflating consistency of a design system with consistency of ux metaphors. I worked on the team that built the new home page dashboard and my experience with the components and associated guidance was excellent.
It is not the fault of the design system that service teams, for example, created 5 different interactions for deleting a resource.
AWS leaned hard into building as many services as possible, at the expense of console ui consistency. There is now a swing back toward consistency, and I expect to see more improvements at the "consistent metaphors" level soon.
You should be using OnPush everywhere, then your struggle will change to only getting changes detected in certain scenarios. Still a pain sometimes but not as bad as the Default change detection strategy.
We use .NET core in production and are very happy. A mixture of EF Core (for ad-hoc queries) and Dapper (for stored procs) works just fine. Also, new in EF Core 2.1, you can map views and stored procs just fine: https://docs.microsoft.com/en-us/ef/core/modeling/query-type....
That's your only specific example - what other functionality are you missing?
You're not willing to commit to .NET core but you admit that NetFx is going into maintenance mode?
Have not yet tried printing and folding one yet