#012 — InertiaJS: SPA Without a Separate API? · Oleh Talanov
Date: July 31, 2026 | 19:00 London / 21:00 Kyiv
Format: Technical discussion · ~60–90 min
Guest: Oleh Talanov
YouTube: https://youtube.com/live/Aq1-dGnv4II
Participants
Oleh Levchenko — Senior Full Stack JavaScript Developer (React / Node.js / AWS)
The AA · Cardiff, UK
YouTube @zloyleva · itfriday.community
Oleh Talanov — CTO & Co-Founder
WebCap Digitals · Zaporizhzhia, Ukraine
LinkedIn · webcap.com
CTO and co-founder of WebCap Digitals — helping Seed/Series A startups accelerate development velocity on Laravel + Inertia.js + React. Second appearance on IT Friday — first was #005.
What We'll Discuss
What problem InertiaJS solves and why it's called the "modern monolith" — a client-rendered SPA built directly on a server framework, no separate REST/GraphQL API layer.
- Comparing approaches: Inertia vs SPA+API, vs Next.js/Remix, vs plain MPA, vs Livewire
- Oleh's practical experience: when to reach for Inertia for Seed/Series A startups, and when not to
- Where Inertia breaks down at scale — coupling, SEO/SSR, server load
- Inertia v2 (2025): async core, prefetching, deferred props — and honest criticism of the approach
Key Takeaways
To be added after the stream.
Timecodes
To be added after the stream.