I have a quick question: When using ABP Studio to create a microservice-based application with an Angular frontend, it generates sub Angular projects for each .NET microservice.
Is it possible to run and host each frontend subsystem independently (as a standalone Angular application)? Or are these projects tightly coupled as modules within the main Angular application and cannot function separately?
1 Answer(s)
-
0
Hello, In the Angular frontend generated by ABP Studio for a microservice-based architecture, each subproject typically corresponds to an Angular library.
These frontend "subsystems" are not standalone Angular applications by default — they are structured as libraries, meaning they are meant to be consumed by a root Angular application (the host app). This structure promotes code sharing and encapsulation across microservices.
However, it is technically possible to host each subsystem as an independent Angular application, but this requires:
- Creating a new Angular application shell for each library.
- Wiring up routing, environment configs, and bootstrapping logic manually.
- Ensuring each new app has access to shared services (e.g., authentication, theming, localization) if needed — which might involve refactoring common modules into shared libraries.
So, while they're not tightly coupled to the main app and can be decoupled, they’re not standalone out-of-the-box. Making them standalone would involve restructuring and setting up new applications that consume these libraries independently.
