platform

Standardize auth wrappers and config decoding across services by extracting duplicated boundary logic into a shared platform library. This enforces consistent inputs/outputs typing, cancellation support, and stable error mappings to prevent cross-service inconsistencies.

Preventing a utils junk drawer anti-pattern requires establishing a disciplined set of shared platform primitives. Apply a clear two-consumer rule and structured migration paths to ensure boundary wrappers remain standardized and predictable.

Implement resilient RPC and HTTP helpers by standardizing resilience patterns and lifecycle hooks within a shared platform library. This enforces explicit time budgets, cancellation support, and stable error mappings across all service boundary interactions.

Maintain low-cardinality telemetry fields and observability logs by standardizing cross-cutting diagnostics within a shared platform library. This ensures consistent log fields, traces, and metrics labels across all integrated services.

Cross-service platform primitives support predictable lifecycle and resource management through structured start and stop guards. This enforces consistent initialization and predictable shutdown behavior across all services sharing the boundary logic.

You should not extract duplicated boundary concerns into a shared platform library if the two-consumer rule is not satisfied. Premature extraction without multiple services duplicating a concern risks over-engineering and complicating service migrations.