https://github.com/baroxx/microfrontends
This project provides examples for MicroFrontends with Angular
https://github.com/baroxx/microfrontends
angular microfrontends
Last synced: about 2 months ago
JSON representation
This project provides examples for MicroFrontends with Angular
- Host: GitHub
- URL: https://github.com/baroxx/microfrontends
- Owner: baroxx
- License: mit
- Created: 2023-05-28T09:48:57.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2023-07-28T16:28:20.000Z (almost 3 years ago)
- Last Synced: 2025-03-27T06:17:32.176Z (about 1 year ago)
- Topics: angular, microfrontends
- Language: TypeScript
- Homepage:
- Size: 354 KB
- Stars: 1
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# microfrontends
There are the same pros (e. g. freedom of technology choice) an cons (e. g. increased complexity) as for microservices in the backend. This overview shows the pros and cons for the different approaches.
| Approach | Pros | Neutral | Cons |
|---|---|---|---|
| Monolith | - No additional dependencies
- Easier implementation of routing | - Complexity depends on size | - Bad overview (even with modules)
- Scaling of the complete application |
| Web components (Angular Elements) | - Separate deployments
- Easier development (smaller pieces)
- You can choose different technologies | - Complexity depends on number of services
- Separate scaling depends on implementation (lazy loading) | - Additional dependencies
- Dependencies to other services (web components)
- Common styling is getting harder |
| Linked frontends | - Separate deployments
- Separate scaling
- Easier development (smaller pieces)
- You can choose different technologies
- No additional dependencies | - Complexity depends on number of services | - Services need to know each other (URLs for routing)
- Common styling is getting harder |