❔ what do large scale enterprise level applications use?
What does companies usually use out of Angular and React for large scale application with asp.net core api?
I did some research about it and found mostly Angular is used when they use .net as the backend.
What does your company use and why is Angular preferred
20 Replies
Front end isn’t as import as back end for scalability.
We use React.
Even for complex projects?
I already know Reactjs so maybe it would be of some use
I feel like our work project is quite complex.
Ok
So is it common that employees would get to work as full stack with handling both the different technologies (c# and react)
I think it's stupidity, but still asking in case
Our companies policy is to use Angular, but my particular product is in React because it precedes this preference. I’m not entirely sure why they chose angular over react but I understand their desire to have everyone using one framework for easier component reuse and collaboration.
I basically only work in C#. Our bottleneck right now is finding React devs.
<library> dev is kinda mid. Like you'd never find a c++ dev advertising themselves as Qt dev or a boost dev
Please remember that there is no one size fits all solution.
Especially when a corporate is starting a new project, the technology used is decided and argued by the team.
This inherently means, that after the project has grown to an enterprise level application, it will use what was decided in the beginning. Unless, it was decided to replace it with something better.
The easiest part to replace in applications of such a scale is the front end.
So when working on your projects, use what you enjoy.
When working at a company, look at what talent the company has already hired, and what is generally available in the area.
A very unpleasant thing that happened to me, is I've joined a project to be developed in .NET, but some idiot decided to push it on Java and managed to convince the project owner to do so, because Java iS tHe SaMe As c#
Even though the team was comprised of .NET devs.
I'm leaving out crucial details as to how that happened, so don't jump to some theories and conclusions.
its not uncommon to discard the frontend and throw it away, but it is uncommon to nuke the backend
But they can you c# also using the microservice architecture right? And is it usually that easy? I heard it's better for enterprise to make most part of their application with 1 single technology
Depends on how you organize your team and what already exists
E.g., your .NET team is tasked with developing a new service. And this service will have a dependency on some other service made in Java.
You are not going to enforce them to rewrite a working, and tested service to .NET, are you?
In a smaller company that uses one language and one stack, yeah, they'll do it in .NET
Unless there is a good reason not to
Or they like to experiment
I understand it's tough for large application to move that quick
Oh boi, yes it is
For larger companies, removing an old app is a long term project in of itself
I actually never heard (i am junior btw) Java and .net going together into same application...I only know .net or Java being an application's main technology and on top of that they use something lightweight like nodejs for particular services
Because most of the task Java can do that c# does and vice versa
Well applications can talk to each other via some api
Even your .net app can connect to, e.g., google api. Which can be written in anything like Go, Java, Node, or whatever
That is not a rule, but an example
You can create very fast serverless functions with .NET thanks to AOT
Previously you'd probably use something else
if you have 50 workers that know java and 50 workers that know C#, no matter what langauge you pick, you will upset 50 people
that seems right
I have worked in 2 angular projects for nearly 1 year and 1 react app for 2 months. In my opinion Angular is easy to adapt for some OOP programmers like c# or java. And My another opinion is React app can be better in terms of performance and light weight build output. React development needs some problem breakup in different angle for a backend c# developers Especially someone who is working since asp.net web forms days 🙂 . For me angular project structure is more or less like a backend project or asp.net mvc project. Ultimately this factors appeal to the team/architects/stake holders differently. Please correct me If I am wrong .
React is awesome. And it does take some getting used to, but once you do it's a blast. Especially if you are fond of functional programming
Was this issue resolved? If so, run
/close - otherwise I will mark this as stale and this post will be archived until there is new activity.