GraphQL for the photo service, REST for Game Mate
The photo community uses GraphQL and Apollo; Game Mate uses REST and TanStack Query. How I chose their API contracts, database safeguards and tests, then added ESLint rules for code boundaries.
#architecture
Posts with this tag.
Bringing health-check reservations into the existing service
I brought health checks from phone inquiries into portal selection and payment. Adding them to existing programs required separate decisions for registration rights, examination choices, and returning from payment.
Keeping working rules from a prototype migration
A prototype migration involved asking an agent to build similar features repeatedly. I put recurring corrections into skills, then found that short, absolute rules could produce the wrong changes too.
Redrawing FSD boundaries for the codebase
The folders followed FSD, yet placing a new file still prompted another discussion. Moving real code led me to regroup domain code and screen composition and abandon strict URL mirroring.
Sharing a program form across two admin apps
Two admin apps shared program inputs but had different submission flows. I separated field types and API transformations while deciding what to share.
Separating responsibilities in an Electron data-collection app
Adding a recruiting platform also copied the collection workflow. I introduced and then removed NestJS, while keeping request handling, collection order, and site-specific processing separate.