You write an algorithm in PSC 1.0, a small, strict pseudocode language, and PseudoChart draws the flowchart as you type. Errors show on the exact line, each FUNCTION and PROCEDURE gets its own linked page, and charts export as PNG, JPG, SVG or PDF. Saves are versioned, and teams share workspaces. Behind it, eight TypeScript microservices run with Docker Compose behind an Nginx reverse proxy. The team split the work along service boundaries, so all three of us built in parallel.
My role
What I built
Owned infrastructure and CI/CD: Docker Compose, Nginx with TLS, and GitHub Actions with change-based test runs and automated VPS deployment.
Built the API Gateway, the only public entry point: Apollo Server GraphQL, Clerk JWT auth, rate limiting, DataLoader batching and WebSocket subscriptions, with resolvers for files, versions, workspaces, templates, exports and history.
Built the Auth Service: verifies Clerk webhook signatures, syncs users into the local database and resolves workspace roles.
Built the Data Access Service, the only service holding database, Redis and MinIO credentials, on Prisma and PostgreSQL, fanning Redis pub/sub events out to the other services.
Built the frontend shell and analytics in Next.js, including real-time save-conflict detection for concurrent editors.
Wrote integration tests with Testcontainers and Vitest.
Highlights
What we shipped
GraphQL API Gateway with Clerk JWT auth, rate limiting and live subscriptions
Data Access Service: the one service with database, Redis and MinIO credentials
Workspace role-based access control and real-time save-conflict detection
Tests cover sign-up, invites, version restore, every parser error E001–E020, and exports
GitHub Actions CI/CD with change-based test runs and automated VPS deployment
Gallery
Photos
pseudochart.site
Architecture: one GraphQL gateway, REST services inside, one service for data
