ASP.NET

Being a Laravel dev (I've used ASP.net too), I would hands-down recommend Laravel. It's convenient to build on, easy to deploy, and there are plenty of skilled Laravel engineers in almost every country. So if you ever want to bring development 'in-house' or work intermittently with freelancers after you've finished with the agency you're working with, you'll find that quite easy wherever you are.

As has been mentioned, Laravel is very ergonomic for developers and it has an incredible community (mostly filled with really positive people) and ecosystem (lots of ready-to-use open source packages to augment your application with new features).

Development costs for the two I'd expect to be about the same, but possibly the agencies using .net will charge a little more as it has historically commanded a slightly higher price point, but I'm not sure how true that still is.

Both will get the job done perfectly well. Laravel would be my choice.

I love .NET, and have a bit of experience in Laravel (nothing in production though). I would recommend sticking to Laravel for a project like the one you want to do. It is loved by developers for its elegancy and features. Laravel has incredible ecosystem with many packages available to implement features fast and easy. The development cost will be much less than .NET (PHP developers are cheap).

What about maintenance? It is a different story. PHP doesn't scale as well as other technologies, but it will have no problem handling traffic for a website like that.

I would recommend for fastAPI, is a python framework but you can use de laravel to manage some part of the application and use the api to actually make the requisitions, its trully fast. Also you can make the pattern you want in this framework, build the estructure/Design Pattern in your way

Just don't .NET. It was a failed idea from the start. Node and javascript are easier to learn, with much wider adoption, and more active communities.

.NET is an old experiment in using a markup language to separate the UI from the business logic. The idea was that this would allow a small team of hyper-competent engineers to build the tooling and code for a large team of less-skilled front-end developers to leverage. In practice, leveraging that customized UI markup requires understanding and adjusting the underlying code. The result is that any UI change requires a hyper-competent .NET engineer.

However, many larger companies bought into it a long time ago, and now have a hard dependency on old monolithic .NET ecosystems, and they do need .NET developers to maintain them.

So, you can get a well paying .NET job without much difficulty. However, you'll neither like it, nor be doing anything interesting. There's no growth here, only a very long slow death of .NET (that'll probably take another 20 years).

Node and Javascript are sticking around, and still growing.

What I can see, you are confusing yourself, if you studied .Net now it's better to work as .Net developer, and you will find opportunities as fresh. Just search and don't waste your time. After you get more experience in .Net, then you can learn NodeJS if you still need to learn it.

Sounds like you are working really hard at improving your skills. Keep at it. I think something you could look at which you haven't mentioned is learning how to use source control in a team setting. There are many things which using a source control system unlocks. When you work in a team you'll be working on a feature that is part of a bigger project, before your code is inserted into the shared code base someone will usually review it and approve the request to merge your feature into the main code base. It also unlocks concepts such as CI/CD and maybe better ways of work (using a task/bug/test tracking tool) - all none-code skills which are just as important as being a good coder.

I would recommend to watch something about architecture and design patterns on youtube to get a feeling for it. Apart from that you mentioned "how to work in a big real project", I would recommend searching up "scrum"(project management). Also looking into CI/CD continuous integration and deployment will help you as well. But most important is that you stay up to date, since everthing changes all the time. Which also means to not worry to much if you will miss something, because you can't know everything in that field with the current speed going :).

If you already have some knowledge in C# you can go with ASP.NET Core MVC and continue your learning path (if you liked the language in the first place). but both solution will allow you to build an ERP/eCommerce project.

There is not too much difference between Django and ASP.Net Core MVC both follow the same design principles for building application, they both flexible, provide a lot of library, have a great community support..

The downside (thats my opinion) with ASP.Net Core you are going to follow the Microsoft philosophy of doing thing and you will mostly by tight to there products lineup. Instead of Django where you'll have more freedom.

If your concern is - Robustness: both are valid choice - Long Term Support: Go ASP.Net why? Because the project is maintained by Microsoft the chance that the project go unmaintained is low. Django is more Open Source we never know when it will stop be maintained.

The best I can give you, it's to try both and make your own opinion. Build a Proof of Concept and see by yourself.

If you are starting from scratch, I would recommend Express.js as a backend web framework. It is faster and more flexible than Django. Express makes it easy to build web applications offering numerous benefits such as efficiency and quicker development times. Some features that are worth mentioning: middlewares, templating, routing, and debugging.

The most important element that is missing the stack is the database. A Web-Based ERP/Accounting Software require a powerful Relational Database to comply with ACID princliples (Atomicity, Consistency, Isolation and Durability). By atomicity, we mean that that database is able to perform the transactions in an atomic manner. A transaction is just a single unit of work, which can either be one query, or multiple queries. Let's say that we have two accounts. And we need to transfer $100 from account one to account two. Now this transfer is just one transaction, but it is going to consist of three different steps. The first step is checking if the account one does have $100. The second would be upgrading the amount of account one to be $900. And the third would be taking this $100 and making the balance and account two be $200. If the database does support atomic transactions, if one of these three steps fail, the whole transaction should fail. This is what atomicity is.

Consistency means that the database should help in achieving the correct data state, adding certain constraints. We can add a constraint on the amount column that it can never be negative, and the database must make sure that this constraint must always be followed.

Then, we have isolation, which is mainly about the concurrency control. Let's say that we have an account which has $1,000, and there are two persons A and B trying to get the money out of this account. So $1,000 and $100. If we let both of these transaction happen at the same time, this would result in the reduction of $1,100. So the balance will result in the negative $100. Isolation prevents this to happen.

Finally, durability means that once a transaction is committed, the data must be written to the non volatile memory or the storage. So that even if the crash happens or something wrong happens with the database, the data must be there and not be corrupted.

In terms of relational database my recomendation is using Postgres. Postgres is an object-relational database, while MySQL is a purely relational database. This means that Postgres includes features like table inheritance and function overloading. Postgres also adheres more closely to SQL standards.

Hi, if you already knows ASP.NET you should consider nopCommerce, as it's an Open Source platform for e-commerce. It's easy to setup and customize, and you should learn a lot using it. Also, if you are familiar with C# you should use Xamarin to develop a mobile app.

Please take a look at our sql web application constructor. Thanks to the reduced stack, it significantly reduces the development time, and therefore reduces the cost. https://falconspace.site/docs/vvedenie-v-falcon-space--c-chego-nachat

i recommended .NET because the library so rich, you can integrated any sources to computed , compiling, integrating, your apps to high complexity, easy to communicated with SAP BAPI. used Oracle DB, Cheers.

For .NET, it may be better to use Azure Storage, which is supported natively by Microsoft