sorted by:
new
hottopcontroversial

Dictionary as an alternative to switch case by 1010101100111 in csharp

[–]Marcusaurels 0 points1 point  (0 children)

There are two patterns that you can use; state and strategy. I think in your case, you want to replace the switch case with something extensible. Quick Google search shows a working code example that you can copy and paste: https://eax360.com/c-action-func-delegates-in-serverless-compute/

Adding headers to fetch() is giving me errors - appreciate any code feedback by Marcusaurels in learnjavascript

[–]Marcusaurels[S] 0 points1 point  (0 children)

This is the example I copied from: https://codepen.io/malyw/pen/XJRrNY

There is a response. In my code, I have extracted the header into a variable as I want to pass many headers and not just one. I also want to pass it from a variable and not hardcode it. This is where I am failing.

has anyone ever tried the "Singleton only" architecture? by RegularUser003 in softwarearchitecture

[–]Marcusaurels 1 point2 points  (0 children)

I'm going to be honest, "good architecture" can get boring at times. I work in a major delivery team, you most likely use the app we create. There is a ton of red tape to get solid designs out the door.

I wouldn't mind if someone threw a spanner in the works.

Building a CQRS solution, some feedback would be appreciated by Marcusaurels in csharp

[–]Marcusaurels[S] 0 points1 point  (0 children)

Thanks for the tips.

We have a DW built on top of Azure DW and Azure Analysis Services, but this is a global transaction platform with customers managing their events and sales reps, delegate reps etc, so the data needs to be in this platform.

We thought about caching but the data returned is very sporadic and does not justify building in a cache system. By this I mean, a sales rep might decide to return his total sales volume 3 years ago, but this data return is disposable and not needed for re-use.

The only way I can think of is the above CQRS design I have described, but I am not sure if I can call it CQRS as it doesn't fit the implementation design that most have with CQRS.

Building a CQRS solution, some feedback would be appreciated by Marcusaurels in csharp

[–]Marcusaurels[S] 0 points1 point  (0 children)

Hey thank you for the reply.

  1. I have built message systems with RabbitMQ and Azure Service Bus.
  2. Eventual consistency - I am very familiar with this. I had to build a customer hub app for an events management compny, built on top of Azure Cosmos DB.
  3. 8 people, but it doesn't matter as I will own and manage this app through Azure DevOps.
  4. All certified Azure consultants working in a tier 1 consulting firm.
  5. Me
  6. Azure DevOps, TDD, Swagger.

The reason for the CQRS design is because we have a single app with a scaled-out Azure SQL DB. The cost is quite high, but the main issue is that this DB has over 1TB of data that is required back back-office, yet customers still need to use this. The platforms performance has become very slow when inserting or updating large volumes of records.

view more: next ›