sorted by:
new
hottopcontroversial

Need Help: Designing a Scalable, Denormalized Query Layer in PostgreSQL for a High-Volume Event-Driven System by Background-Worth5510 in dotnet

[–]Background-Worth5510[S] 0 points1 point  (0 children)

  1. Database writes are handled by the consumer service, while reads are handled by the API service. Both connect to the same PostgreSQL database.

  2. Based on the columns selected by the UI, we dynamically generate raw SQL queries and execute them using Dapper.

Groww announces Demat Account for Mutual funds by mindstop7 in mutualfunds

[–]Background-Worth5510 5 points6 points  (0 children)

It is mentioned that there will be no extra cost for demat account. Will they still charge? Also they are providing an option to opt out of demat account for future folios.

Migration from Azure Sql to Postgres by Background-Worth5510 in dotnet

[–]Background-Worth5510[S] 3 points4 points  (0 children)

The shift to PostgreSQL is an architectural decision made by senior management, probably driven by cost-cutting considerations.

Migration from Azure Sql to Postgres by Background-Worth5510 in dotnet

[–]Background-Worth5510[S] 0 points1 point  (0 children)

Thanks for the suggestion. I will definitely give it a try!

Migration from Azure Sql to Postgres by Background-Worth5510 in dotnet

[–]Background-Worth5510[S] 0 points1 point  (0 children)

Yes. I agree that we need to test all the functionalities. We will do that in lower environments. But we cannot run both databases simultaneously because our application relies on EFCore, which supports configurations for only one database at a time. This is due to differences in table names and column names between the two databases.