Take Everywhere Platform | Taylor Frank

Context

Legacy fulfillment and product workflows were split across disconnected services, slowing feature delivery and making incidents hard to triage.

Constraints

• Needed to support ongoing feature delivery while reworking core platform boundaries.
• Multiple teams depended on legacy integration paths with limited observability.
• Operational tooling had to improve without introducing migration downtime.

Introduced a platform boundary with clear domain APIs, shared event contracts, and an operational dashboard layer for lifecycle visibility.

Step 1

Domain API ingress

Requests enter through domain APIs with auth, input validation, and consistent request contracts.

Step 2

Workflow orchestration

Business workflows are orchestrated through service boundaries and event contracts to reduce coupling.

Step 3

Lifecycle state store

Operational state is persisted for traceability and to support recovery actions during failures.

Step 4

Operator visibility

Dashboard surfaces status transitions, errors, and intervention points for support and operations.

Domain API boundaries

Tradeoff: Required contract discipline and refactoring effort, but reduced service coupling and release risk.

Shared lifecycle event contracts

Tradeoff: Introduced event schema governance overhead, but enabled clearer ownership across workflows.

Operator dashboard layer

Tradeoff: Added a maintenance surface area, but reduced diagnosis time and support load.

Architected and owned a cloud-native platform serving thousands of users across thousands of school and district access contexts.

Built internal APIs, order flows, operations dashboards, uploads, reporting, and secure middleware patterns.

Operated across application, data, and infrastructure layers with end-to-end ownership.

Expanded school and district access contexts from 2,100 to 6,000+ in under a year.

Cut average incident diagnosis time by centralizing lifecycle state and internal tooling.

Improved release confidence with stronger service boundaries and contract discipline.

Next.jsTypeScriptNode.jsPostgresDynamoDBAWS

Platform refactors land faster when observability improvements ship in the first wave.
Small schema review rituals prevent costly contract drift later.

I can walk through tradeoffs, incident patterns, and architecture details live.