Skip to content

Latest commit

 

History

4 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 

Repository files navigation

Isaac Gitonga

Principal Architect. I design and build software systems where data correctness, security, and transaction integrity are non-negotiable. My focus is on database transaction boundaries, concurrency protection, and structural isolation—engineering platforms to withstand stress without compromising data state.

I care deeply about how things work — from UI rendering and animation pipelines, down to data modeling, system boundaries, and execution trade-offs.


What I Work On

  • System Design & Architecture
    • Backend-for-Frontend (BFF) patterns
    • Domain-driven design and decoupled, layered architectures
    • Repository patterns for transaction safety
  • Web Engineering
    • Data-heavy UI and dashboard architecture
    • Scroll-driven and interaction-based storytelling
  • Data & Infrastructure
    • PostgreSQL (relational database modeling and indexing strategies)
    • Type-safe data access layers
    • Pragmatic deployment workflows and Linux infrastructure

Selected Work

  • SaaS Ticketing Platform – High-concurrency event transactions, pessimistic locking boundaries, multi-tenant RBAC, and database-level inventory safety.
  • Government Services Platform – Multi-agency workflows, PostgreSQL database models, and BFF architecture.
  • Developer Portfolio – Performance-focused, animation-driven motion systems.

Detailed case studies and system breakdowns live here:
👉 isaacgitonga.com


Core Stack

  • Backend & Orchestration: Node.js, Express, Next.js (App Router), TSyringe, Prisma ORM
  • Databases: PostgreSQL, MySQL, Redis
  • Frontend: TypeScript, React, Tailwind CSS, GSAP (ScrollTrigger & Motion Timelines)
  • Infrastructure & Tooling: Neon, Cloudflare (object storage), Netlify, Vercel, Linux, Git

Philosophy

  • Architecture is not about overengineering — it’s about making change cheap.
  • Performance is a feature, not an afterthought.
  • Motion should serve clarity, not decoration.
  • Strong abstractions must earn their keep over time.
  • Understand fundamentals first, then scale complexity deliberately.

I use GitHub to ship real systems, explore architectural ideas, and refine engineering judgment — not just to collect stars.

About

Full Stack Web Developer

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors