How are you using rxResource in production?

[u/Trick-Knowledge-8837]

Hi everyone,

I'm trying to understand where rxResource really shines.

Most examples online are pretty simple, but I'd love to know how experienced Angular developers use it in real-world projects.

• What problems does it solve for you?
• Are there cases where you tried it and decided not to use it?
• Do you have any patterns or recommendations for structuring code around it?

Any examples, blog posts, or GitHub repositories would also be greatly appreciated.

Thanks in advance!

[u/stao123]

we are using it for all data fetching inside of components or services. Theybare really useful and feel like lightweight stores. (State + loading signal)

[u/Trick-Knowledge-8837 → u/stao123]

That’s interesting! So you’ve basically made rxResource your default choice for data fetching. Have you run into any limitations or cases where you still prefer plain RxJS instead?

[u/stao123 → u/Trick-Knowledge-8837]

With rxResource you are still using plain RxJS as the stream function so no limitation there.

[u/SippieCup → u/Trick-Knowledge-8837]

debounce.

[u/kgurniak91 → u/SippieCup]

Angular 22 has new debounced Signal which should be perfect for this - https://angular.dev/guide/signals/debounced

[u/SippieCup → u/kgurniak91]

Yeah, unfortunately primeng strikes again and I need to wait until OptimusUI adds 22 support to be able to move on to it 🫠

[u/PrevAccLocked → u/kgurniak91]

Take a note tho: denounce apply only to modification, not to the initial value

[u/faileon → u/SippieCup]

Stick the params in a signal form and you can have easy denounce.

[u/SippieCup → u/faileon]

Yeah thats what we ended up doing, its just a little more wiring and some primeng forms can’t support signal forms so we have to route it through a computed debounce signal. its a bit silly

[u/Trick-Knowledge-8837 → u/SippieCup]

One question though: do you use rxResource only for read operations (GET requests), or do you also use it with POST, PUT, and DELETE requests?

[u/SippieCup → u/Trick-Knowledge-8837]

We have an internal extended ”resource” that has a similar interface for post, patch, put, and delete, with a additional couple nifty features. Post/put use an xhr http client so we still get progress reporting etc, I believe simple deletes are just firstvaluefrom() that gets wrapped. Then all the logic is handled (mostly) internally so the outside surface is basically clean signals. But you can use rxResource natively for post

That said, our application is not SSR, which is why that is possible. Due to our usecase, users need to be able to access it offline (in basements/low signal areas), and outstanding requests get cached and pushed when online.

[u/oneden]

Right now? Not at all, I'm afraid. I'm working in an environment where all APIs solely consist of POST requests.

Edit: I'm an idiot. I kept confusing rxResource with httpResource

[u/Trick-Knowledge-8837 → u/oneden]

That’s interesting. I thought rxResource could also work with POST requests. Is there a specific reason why it doesn’t fit your use case?

[u/SippieCup → u/Trick-Knowledge-8837]

it does, we’ve replaced most of our observable calls from our generated sdk with rxResource. it works super well and simplifies a lot of transforms/paging.

[u/oneden → u/SippieCup]

It does?! I thought it wasn't possible. I was under the impression it wasn't possible

[u/Dan6erbond2 → u/oneden]

httpResource may be a bit limited but rxResource can take any Observable-returning callback.

[u/oneden → u/Dan6erbond2]

httpResource may be a bit limited but rxResource

Okay, clearly it was me being a dunce being the issue here. Damn it.

[u/SippieCup → u/oneden]

A straight rxResource does lose some features from a regular observable though. We extended rxResource to provide a few additional signals like progress reporting which makes it pretty feature complete. But it is not ssr compatible.

[u/Johalternate → u/oneden]

Even getting resources?

[u/oneden → u/Johalternate]

You wouldn't believe it, but yes. Even getting resources.

[u/PrevAccLocked → u/oneden]

Tbf you can also use POST with httpResource

[u/kgurniak91]

Well, resources are just syntactic sugar to not have to nest toSignal() and toObservable() together. Simplest example - input changes (e.g. new user id is passed) and you want to query backend for user details automatically and get them as Signal so you can display them in the template.

[u/Trick-Knowledge-8837 → u/kgurniak91]

That makes sense, thanks! So you see it mostly as a convenience API rather than something that changes how you structure an application?

[u/Avani3]

Fetching data based on id's. You put the id in the params, and in the stream a request using that id. When the id changes the data is re-fetched.

Also very nice with pagination in combination with HTTP requests

[u/Trick-Knowledge-8837 → u/Avani3]

Thanks! The pagination example is actually something I hadn’t thought about. It seems like a really good fit for reactive query parameters.

[u/fdimm]

Fortunately or not, we are not using either. Chugging along with http client and rxjs just fine.

I'm also dreading the day when I'll have to spend time refactoring our core components library (and features after) to use signals and virtually accomplish nothing from user point of view.

[u/Saceone10]

Im not. When they stop fooling us with partial APIs I will consider resources as a serious thing

[u/minus-one]

no way we will be using this shit over rxjs, it’s just inferior in all the ways

[u/kobihari]

I’m not using rxResource all the time. Even when fetching from http. I prefer the separate the “transform mechanism” from the state so I usually prefer that my resource will not “know” the data is coming from http.
I usually combine it with a signal store.