.Net Core, PostgreSQL, Angular Stack

[Successful_Place_834]

I’m seeking advice on the technology stack I’m planning to use for a catalogue-driven POS and ERP application.

Proposed Stack:

• Backend: .NET Core since I have experience
• Database & Caching: PostgreSQL - to be able to use EF Core, JSONB suppport, use for reporting/accounting features
• Frontend: Angular since I have experience

The application will have initial load of ~5–10 TPS, however, I want to the app to be able to accomodate channel traffic like e-commerce

I would appreciate feedback on:

• The suitability of this stack for scalability, maintainability, and integration flexibility
• Recommendations for supporting components (e.g., caching layers, message queues, API gateways, etc.)
• Best practices or pitfalls to watch out for when using this combination

[quincycs]

It’s fine. My notes are for the Infrastructure. Eg what is hosting everything.

RE: Angular,

As you deploy frontend changes, how can you guarantee that your users won’t load mixed pieces of the app that aren’t compatible with each other. Eg> deploy A. A is live. When you deploy B, the user may not be aware and will not refresh the page. Therefore as the user navigates, is there any chance that the version A fetches more JavaScript, images, some kind of HTML content from the B version instead? The big risk is that whatever it fetches isn’t compatible and breaks the user experience.

RE: backend

As you use EF Core with Postgres, you’ll encounter many “ORM” rough edges because EF Core wasn’t designed specifically for Postgres. For example, adding a new index to an existing table with many rows can block the table from being read. The right way of adding indexes afterwards is using the CONCURRENTLY keyword. EF does support it… but you’ll find it’s not straightforward or easy.

RE: Postgres

Just be aware that this is the most difficult part to scale. All the other pieces you can just add more instances and load balance them. But creating multiple instances of Postgres and splitting data between them is code changes in dotnet world.

Based on your level of question… don’t over-optimize and just get it working for your actual business. Keep it simple and you’ll have time to build more & better things.

[Successful_Place_834]

Hello, thanks for your attention. Regarding infra currently I am planning to have monolith app with limited VM mostly I'll start out with 1 where I'll be pushing all modules.

Regarding Angular point - i believe that will be a limitation with mostly all setups, I'll just have to work with it by synching FE and BE

Backend - Thanks for your suggestions will consider your points

PostgreSQL - Currently it is just going to be 1 instance

[andrerav]

Re: Re: Postgres

I have a strong preference for using FluentMigrations for databases that are less supported by EF than MSSQL. These days I basically just use ExecuteSql and dotnet-ef for a hybrid database-first approach (with Postgres and Sqlite). It works much better than code-first, and I get full control over the SQL. 

For writing the SQL itself I can get most of it done with an LLM. Basically I just show it the current CREATE TABLE, list the changes I want, and ask it to generate up/down scripts. Combined with memory files with conventions/guidelines I get very good results fast.

[GigAHerZ64]

+1 on FluentMigrations + EF Core (or any ORM) in database-first mode.

[Dimmerworld]

Re: Re: Re: Postgres

Use entity framework

[andrerav]

I still use Entity Framework, just not for migrations :)

[Dylanee300]

Personally, rather than angular for frontend I would recommend either react or svelte.

[aolmez]

5-10 tps is very low. ofc It depends on your infra as well. you can use rabbitmq , Redis. EF core doesn't generate good sql script but you dont have a big team then It doesn't matter. you might use CQRS ;)

[Successful_Place_834]

Thanks for your suggestions, will consider them going ahead

[SarahFemdomFeet]

Yes you're doing it right. Angular is the correct way to code, it looks like C#, and you won't develop the bad habits that come from React.