effect-patterns

Effect-TS services use three canonical patterns: Effect.Service for simple cases, Context.Tag with class extension for strategy-based approaches, and Context.Tag with Config for flexible configuration. Each enforces type-safe construction and auto-provided dependencies, ensuring consistent architecture across your application.

Use Atom.make() from effect-atom for reactive, performant state management. This pattern avoids Effect.Ref complexity while maintaining type safety and enabling reactive updates that integrate seamlessly with React components and Effect-TS services.

Apply Schema.TaggedStruct or Schema.TaggedClass for robust domain modeling and data validation, combined with Effect.withSpan for distributed tracing. These patterns ensure type-safe serialization, runtime validation, and observable architecture across your services.

Effect.Service provides straightforward service definition with automatic dependency provision. Context.Tag with class extension implements the Strategy pattern for behavioral flexibility. Context.Tag with Config enables runtime configuration without modifying code, each suited to different architectural needs.

Layer-driven runtime composition orchestrates service dependencies declaratively. Define services with their patterns, specify Layer dependencies, and compose them into a coherent runtime. This approach scales horizontally and maintains explicit readonly interfaces via as const.

Yes. Effect-TS patterns apply across service definition, dependency injection, and layering for backend services, while effect-atom provides React state management following the same architectural principles. This creates consistency between server and client-side code.