back to homepage
Back-End Engineering
APIs, services, and data layers by Kacper Michalik—Node.js, NestJS, PostgreSQL, GraphQL, and tRPC.
Kacper Michalik’s back-end engineering covers APIs, services, and data layers: Node.js and NestJS services, PostgreSQL and Redis for persistence and caching, and GraphQL or tRPC for typed client–server contracts. He designs interfaces that stay reliable as products grow past the MVP stage.
Focus
- Typed API design (REST, GraphQL, tRPC) with clear domain boundaries
- PostgreSQL data modeling, caching with Redis, and pragmatic persistence choices
- Service structure with NestJS for maintainable server applications
- Local and production-ready setups with Docker for fast iteration
Stack
- Node.js
- NestJS
- TypeScript
- PostgreSQL
- Redis
- GraphQL
- tRPC
- Docker
In production
- Screen Studio — API and infrastructure layers supporting a production macOS product.
- Open-source System Design guide — architecture, scalability, and fault-tolerance notes for engineers.
- Published guides — tRPC vs GraphQL vs REST (SD Times) and PostgreSQL with NestJS & Docker (HackerNoon).
Frequently Asked Questions
What back-end technologies does Kacper Michalik use?
Kacper Michalik builds services with Node.js and NestJS on TypeScript, uses PostgreSQL and Redis for storage and caching, and chooses GraphQL or tRPC when typed client–server contracts improve delivery speed and safety.
How does Kacper choose between tRPC, GraphQL, and REST?
He weighs team velocity, client needs, and operational complexity. He has written publicly on choosing the right API design for modern web applications (SD Times), favoring clear contracts and pragmatic trade-offs over dogma.
Where is his back-end work used in production?
Back-end work supports Screen Studio and is reinforced by an open-source system design guide plus practical writing on NestJS, PostgreSQL, and Docker for local development.
Related expertise
Related
