DEV Community: Ali Bayat

Answer: How do I update an existing document inside ElasticSearch index using NEST?

Ali Bayat — Mon, 20 Dec 2021 00:16:51 +0000

Nov 13 '19

A better solution in Nest 7.x:

await _client.UpdateAsync<ElasticSearchDoc>(doc.Id, u => u
  .Index("movies")
  .Doc(new ElasticSearchDoc { Title = "Updated title!" }));

Open Full Answer

Answer: Why are commands and events separately represented?

Ali Bayat — Mon, 16 Aug 2021 04:21:30 +0000

Mar 24 '19

The event is a fact from the past.

The command is only a request, and thus may be refused.

Commands	Events
Purpose	Invoke Behavior	Something Happened
Ownership	Command Owned by Consumer	Event Owned by Publisher
Consumers	One Consumer	Zero or Many Consumers
Senders	Many Senders	Single Publisher
Naming	Verb	Past

…

Open Full Answer

Answer: When to use record vs class vs struct

Ali Bayat — Wed, 19 May 2021 14:17:22 +0000

May 19 '21

You can use structure types to design data-centric types that provide value equality and little or no behavior. But for relatively large data models, structure types have some disadvantages:

They don't support inheritance.
They're less efficient at determining value equality. For value types, the ValueType.Equals method…

Open Full Answer

Answer: Annotation-Based vs Code-First in Hot Chocolate

Ali Bayat — Wed, 14 Apr 2021 10:37:07 +0000

Apr 11 '21

Annotation-Based or Pure Code-First: In this approach, we don't bother about GraphQL schema types, we will just write clean C# code that automatically translates to GraphQL types.

Code-first: In this approach, we use Schema types, Schema types allow us to keep the GraphQL type configuration separate from…

Open Full Answer

Answer: What is the difference between the Facade and Adapter Pattern?

Ali Bayat — Mon, 15 Jun 2020 07:26:58 +0000

Jun 15 '20

The main goal of the Facade pattern is to make the class or subsystem easier to use, while the main goal of the Adapter pattern is to adjust the interface to what the client expects.

Open Full Answer

IOptionsMonitor vs. IOptionsSnapshot

Ali Bayat — Thu, 21 May 2020 07:32:58 +0000

https://stackoverflow.com/a/61929399/3427324

What is Data Partitioning?

Ali Bayat — Tue, 14 Apr 2020 16:05:35 +0000

The data storage for a software system can often be a bottleneck. If you try to run an application using a single database server, as you scale, you'll soon reach the limits of a single machine, even as you pay for a bigger, more expensive machine with more CPUs and memory. This is where data partitioning can help.
Here's a simple example. A block blob in Azure Storage currently has a maximum size of just under 5 TB. Five terabytes is a large blob, but what if you have 8 TB of data to store? Well, you'd need to partition your data across multiple blobs. You could, for example, store 4 TB in blob 1 and another 4 TB in blob 2.
That's a simple example of partitioning. Now let's talk about three specific types of partitioning. First, imagine you need to store orders in your application and an order consists of five attributes. We'll just call them A, B, C, D, and E. These attributes could be columns in a relational database or properties in a document-oriented database, but let's also say that the application frequently accesses attributes A and D, but rarely accesses B, C, and E.

In that scenario, we can vertically partition orders so that A and D are stored separately from B, C, and E. This could have a few benefits. For example, there could be less contention in a database if the attributes are separate and the tables are not as wide, or we could store A and D in fast premium storage while B, C, and E stay in less expensive storage. Also, A and D would be less information and easier to cache and faster to replicate so there are several opportunities when using vertical partitioning to optimize your data.

Another approach with orders is to spread the order data across multiple data sources. This is what we call horizontal partitioning, and horizontal partitioning is a popular approach to scaling data because this approach gives you a lot of power that you can use for scalability and performance. One approach to horizontal partitioning is to use what we call range partitioning. I could say that all the orders for customers A through M go to one database, while all the orders for customers M through Z go to a different database. A range could also be temporal. So I could say all the orders for this month go to one database and all the orders for last month go to a different database, or I could have a hashing algorithm that places orders into different databases in a more round-robin fashion. You can almost think of it like load balancing for databases. The choice here really depends on the application and the data and how the data is used, but in a horizontal partition, I used the same schema or same document shape in all the different databases, but since I'm spreading the data out, it's easier to scale out my hardware and add more processing power as my data grows.

Finally, there's also what we call functional partitioning. Let's say for this scenario our system stores orders and also stores invoices. In functional partitioning, these two datasets could live in different data sources that are optimized for the data and the system that uses the data. So we could use a relational database for orders and a document-based database for invoices. This sounds complicated, which is true. You don't necessarily want to use functional partitioning for a simple application, but for large systems, for large data, for a scalable system, functional partitioning is one partitioning strategy to evaluate so you can match up the best data store for your data and application data access patterns.

So I can not tell you which partitioning strategy is best for your application. I can just tell you that if you need to be highly scalable, you should evaluate a partitioning strategy and yes, partitioning can complicate your design and implementation. It can be difficult, for example, to join data across partitions or enforce transactions across partitions.

How can I optimize read access?

Ali Bayat — Thu, 26 Mar 2020 17:37:38 +0000

Jul 25 '16 Comments: 1 Answers: 2

I work on data that is mostly read and I want to perform these works as efficiently as possible, and I need to provide thread-safe access to it.

Any explanations on my problem would be welcome. Thanks

Open Full Question

HTTP Error 500.19 in IIS 10 and Visual Studio

Ali Bayat — Fri, 28 Feb 2020 17:36:44 +0000

Sep 5 '17

Press Win Key+R to Open Run Window
in the Run Window, enter "OptionalFeatures.exe"
in the features window, Click: "Internet Information Services"
Click: "World Wide Web Services"
Click: "Application Development Features"
Check the features.

I'm using Windows 10

Note: "You must be signed in as an administrator to be able to…

Open Full Answer

What are the differences between app.UseRouting() and app.UseEndPoints()?

Ali Bayat — Fri, 28 Feb 2020 08:31:50 +0000

Jan 29 '20

UseRouting: Matches request to an endpoint.

UseEndpoints: Execute the matched endpoint.

It decouples the route matching and resolution functionality from the endpoint executing functionality, which until now was all bundled in with the MVC middleware.

This makes the ASP.NET Core framework more flexible and allows other middlewares to…

Open Full Answer

Answer: HttpClientFactory.Create vs new HttpClient

Ali Bayat — Thu, 27 Feb 2020 12:49:28 +0000

Feb 27 '20

IHttpClientFactory offers the following benefits:

Naming and configuring logical HttpClient instances.
Build an outgoing request middleware to manage cross-cutting concerns around HTTP requests.
Integrates with Polly for transient fault handling.
Avoid common DNS problems by managing HttpClient lifetimes.
Adds logging for all requests sent through clients created by the factory.

…

Open Full Answer