Optimize ElasticSearch Data Seeding by using bulk indexing instead of sequential indexing (Dashbaord Service).

[amrali21]

Description:

Currently, the Dashbaord service indexes seed data documents one-by-one during startup, which creates significant delay (about 10 minutes on my pc) before the service can start. this can be seen in the SeedData function here:

dotnetcore-microservices-poc/DashboardService/Init/SalesData.cs

Line 19 in 6500daa

public async Task SeedData()

Fix:

This can be optimized by implementing bulk indexing. which basically means we index all the documents all at once in one go.

I've tried this solution locally and it ran x10 times faster. I know this is a simplified project is for education purposes but it would be nice if we implemented bulk indexing as it follows Elasticsearch best practices.

If you can confirm this issue, i could go ahead with a PR if needed.
Thanks.

[wojteksuwala]

Thank you for the suggestion, and I apologize for the long delay. PRs are very welcome, but please implement changes against the https://github.com/asc-lab/dotnetcore-microservices-poc/tree/dotnet9migration branch, where all features have been migrated to .NET 9.

[amrali21]

Thank you for the suggestion, and I apologize for the long delay. PRs are very welcome, but please implement changes against the https://github.com/asc-lab/dotnetcore-microservices-poc/tree/dotnet9migration branch, where all features have been migrated to .NET 9.

Done . and sorry for delayed response.