business and framework

[bucurdavid]

Could you help me understand why framework-specific logic, like createAsyncThunk, is included in the business layer?

cc: @Abouelyatim

[BastienCorre]

Hi, just passing by to check out some clean architecture repositories. I’ll give you an answer—maybe not the one the repo owner would give, but still an answer.

Architecture is all about trade-offs. If you want to remove React from the core (i.e., the business layer), you need to replace it with something else. For instance, you could use something like Redux and its createAsyncThunk, which can be applied in other JS/TS frameworks as well.

You can absolutely implement clean architecture without RTK (Redux Toolkit), but if you choose to stick with it, it makes perfect sense to include it in the business layer of your application.

Was this helpful?

[bucurdavid]

Hi, @BastienCorre and thanks for the answer. Absolutely, this makes sense! When considering trade-offs, the app's structure is fundamentally built around React, and with a few adjustments, it could potentially work in Next.js or other JS/TS frameworks. However, switching to a completely different language or framework would require a full redesign.

In cases like this, where we anticipate staying within the React/Next.js/JS ecosystem, having a dedicated framework folder might feel like an unnecessary overhead. Instead, the focus should be on achieving proper abstraction and separation of concerns between third-party dependencies and the React app itself. This approach keeps the project streamlined and better aligned with the anticipated ecosystem.

[BastienCorre]

I understand your viewpoint but I think it can go yet a little further. I’m currently working on a clean architecture starter using Redux in a React/Next.js/Remix environment. If you're interested, I’ll ping you later so we can share our thoughts.