Common Questions

[oleksii-shepel]

Q: What is actionstack?

Actionstack is a state management library built on top of streamix.

It combines:

• actions
• reducers
• reactive streams
• modules
• strongly typed APIs

into a single reactive architecture.

---

Q: Is actionstack another Redux clone?

No.

Actionstack borrows familiar concepts such as actions and reducers, but it is built around reactive streams rather than a centralized dispatch loop.

The goal is not to recreate Redux.

The goal is to make state feel like a natural part of a reactive system.

---

Q: Why use actions at all?

Actions provide explicit intent.

userActions.login(credentials);
userActions.logout();

Instead of asking:

"What changed?"

you can ask:

"What happened?"

That distinction becomes increasingly valuable as applications grow.

---

Q: Does actionstack require reducers?

Reducers are supported because they remain a simple and predictable way to update state.

on(userActions.rename, (state, action) => ({
  ...state,
  name: action.name
}));

The question is not whether reducers are fashionable.

The question is whether they remain understandable.

---

Q: Why not just use signals?

Signals are excellent for local reactivity.

Actionstack focuses on application-wide concerns:

• actions
• feature boundaries
• state transitions
• shared workflows
• predictable behavior

Signals and actionstack can complement each other rather than compete.

---

Q: Is actionstack reactive?

Yes.

State can be consumed as streams and composed with the rest of the streamix ecosystem.

userModule.state$
  .pipe(
    map(user => user.name)
  );

Reactive composition is a first-class concept.

---

Q: Is actionstack intended for large applications?

Yes.

The module architecture is designed to help organize applications as they grow.

Features can remain isolated while still participating in a shared reactive runtime.

---

Q: Does actionstack support async operations?

Yes.

Modern applications spend much of their time waiting for something:

• APIs
• databases
• workers
• storage
• AI services

Actionstack is designed to work naturally with asynchronous workflows rather than treating them as special cases.

---

Q: Is actionstack global-state only?

No.

Applications usually contain multiple layers of state:

• local state
• feature state
• shared state
• application state

Actionstack focuses on coordinating state where shared behavior becomes important.

---

Q: What is the philosophy behind actionstack?

Keep state predictable.

Keep behavior explicit.

Keep modules isolated.

Let actions describe intent.

Let reducers describe transitions.

Let streams handle reactivity.

Everything else emerges from composition.