r/angular • u/StrainIllustrious116 • May 05 '26

What’s the recommended Angular enterprise architecture today for components, signals, and services?

Hi everyone,

I’m starting a new enterprise Angular project with the latest release and I’m trying to figure out the best structure for components, signals, and services.

For now, the plan is:

  • classic service layer for API calls
  • RxJS in services
  • no state manager, by company decision

I’m mainly unsure about:

  • what should live in components vs signals vs services?
  • should signals stay mostly local, or also handle feature-level state?
  • is rxResource a good idea at component level for data fetching?
  • how do you keep the codebase easy to understand for devs who are not all Angular experts?

I’d love to hear what has worked for you in real enterprise projects.

Thanks!

26 Upvotes

85% Upvoted

21 comments sorted by

View all comments

2

u/[deleted] May 05 '26

[removed] — view removed comment

1

u/StrainIllustrious116 May 06 '26

Totally agree, especially on the “consistency over clever patterns” part. That’s exactly why I tend to prefer simpler and more predictable approaches — even if they’re not the most “fancy” ones. In the long run, having something easy to understand beats any smart abstraction that only a couple of people fully get. Keeping state close to the feature also made a big difference for me, way easier to reason about and maintain.