Daniel Fridkin · Home
עברית
עברית
Back to projects

Full-stack Engineering / Platform Modernization

KSP Storefront

Consolidation of five legacy storefronts and services into one server-rendered Next.js application, with scoped data endpoints, Redis read budgets, and Kubernetes delivery.

In development

Consolidation design · in development

Shared storefront with controlled data reads

One Next.js application consolidates legacy storefront behavior while scoped read budgets and Cloudflare origin controls limit unrestricted data access.

  1. Render shared experiences

    Serve web, internal web, mobile, and self-service experiences from one codebase with server-rendered SEO routes.

    • Next.js 16
    • React 19

  2. Govern remaining data reads

    Scope data endpoints and count session and client budgets, with a log-then-enforce rollout.

    • Redis
    • Cloudflare

  3. Validate and deliver

    Verify production parity and microfrontend contracts, publish images through CI, and deploy separate Kubernetes workloads through GitOps.

    • GitLab CI
    • Argo CD
    • Kubernetes / OKE

The challenge

Separate desktop, mobile, kiosk, and branch front ends, plus a PHP bot pre-render service, duplicated storefront behavior while a public data API enabled unrestricted automated catalog reads.

The approach

Building one Next.js 16 and React 19 codebase for four Kubernetes workloads, combining server-rendered pages, scoped session and client read budgets, and an origin restricted to Cloudflare with production parity checks and separate CI and GitOps deployment workflows.

My role

Built the shared storefront and platform integrations using AI-assisted implementation and review, production-browser parity checks, automated tests, CI, and staging validation.

Engineering decisions

Combine rendering with explicit read controls

Pair server rendering with scoped data endpoints, Redis budgets, and Cloudflare origin restrictions to control catalog access across page and API reads.

Preserve behavior through consolidation

Use automated parity and microfrontend contract tests while keeping image builds separate from Argo CD deployment.

Scope & delivery

  • One codebase consolidates desktop, mobile, self-service kiosk, branch-computer, and bot pre-render behavior into web, internal web, mobile, and self-service workloads.
  • Next.js Cache Components and blocking SSR for SEO routes, with canonical URLs and device redirects.
  • Scoped data endpoints use Redis budgets per session and client, with a log-then-enforce rollout.
  • Production parity work covers PC builder and bids, payments, Eilat pricing, and cart, user, and chat microfrontend contracts.
  • About 500 automated tests plus Playwright checks verify key behavior and blocking SSR on SEO routes.
  • JSON logs, OpenTelemetry traces through Grafana Alloy, and Prometheus metrics support operations; nginx serves shared static assets.
  • Version notices and an opt-in PWA include an offline page; GitLab CI builds images for separate deployment through Argo CD.
Next projectOCI Frankfurt Multi-AD Production Migration