<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://topzyray.github.io/</id><title>Tope Taiwo</title><subtitle>Tope Taiwo is a fullstack software engineer with 4+ years of experience building production-grade web, mobile, and cloud-native applications with TypeScript, Python, React, React Native, Next.js, NestJS, FastAPI, PostgreSQL, MongoDB, and Redis.</subtitle> <updated>2026-10-13T07:00:44+01:00</updated> <author> <name>Tope Taiwo</name> <uri>https://topzyray.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://topzyray.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://topzyray.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Tope Taiwo </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>RBAC Is Not Enough: Thinking About Authorization in Enterprise Systems</title><link href="https://topzyray.github.io/posts/rbac-is-not-enough-thinking-about-authorization-in-enterprise-systems/" rel="alternate" type="text/html" title="RBAC Is Not Enough: Thinking About Authorization in Enterprise Systems" /><published>2026-10-13T06:00:00+01:00</published> <updated>2026-10-13T07:00:16+01:00</updated> <id>https://topzyray.github.io/posts/rbac-is-not-enough-thinking-about-authorization-in-enterprise-systems/</id> <content type="text/html" src="https://topzyray.github.io/posts/rbac-is-not-enough-thinking-about-authorization-in-enterprise-systems/" /> <author> <name>Tope Taiwo</name> </author> <category term="Backend Engineering" /> <category term="Security" /> <summary>Understand where role-based access control falls short in enterprise systems and why authorization must consider organizational context.</summary> </entry> <entry><title>Sessions, Devices and JWTs in a Multi-Client Application</title><link href="https://topzyray.github.io/posts/sessions-devices-and-jwts-in-a-multi-client-application/" rel="alternate" type="text/html" title="Sessions, Devices and JWTs in a Multi-Client Application" /><published>2026-10-12T08:00:00+01:00</published> <updated>2026-10-11T07:53:41+01:00</updated> <id>https://topzyray.github.io/posts/sessions-devices-and-jwts-in-a-multi-client-application/</id> <content type="text/html" src="https://topzyray.github.io/posts/sessions-devices-and-jwts-in-a-multi-client-application/" /> <author> <name>Tope Taiwo</name> </author> <category term="Backend Engineering" /> <category term="Security" /> <summary>Design production session management for JWT applications, including device tracking, session revocation, and web and mobile clients.</summary> </entry> <entry><title>Designing Authentication as a System, Not a Login Endpoint</title><link href="https://topzyray.github.io/posts/designing-authentication-as-a-system-not-a-login-endpoint/" rel="alternate" type="text/html" title="Designing Authentication as a System, Not a Login Endpoint" /><published>2026-10-11T08:00:00+01:00</published> <updated>2026-10-11T07:53:41+01:00</updated> <id>https://topzyray.github.io/posts/designing-authentication-as-a-system-not-a-login-endpoint/</id> <content type="text/html" src="https://topzyray.github.io/posts/designing-authentication-as-a-system-not-a-login-endpoint/" /> <author> <name>Tope Taiwo</name> </author> <category term="Backend Engineering" /> <category term="Security" /> <summary>Design authentication beyond login by considering verification, recovery, revocation, multiple devices, and web and mobile clients.</summary> </entry> <entry><title>Express vs NestJS: The Framework Should Serve the Architecture</title><link href="https://topzyray.github.io/posts/express-vs-nestjs-the-framework-should-serve-the-architecture/" rel="alternate" type="text/html" title="Express vs NestJS: The Framework Should Serve the Architecture" /><published>2026-10-10T08:00:00+01:00</published> <updated>2026-10-11T07:53:41+01:00</updated> <id>https://topzyray.github.io/posts/express-vs-nestjs-the-framework-should-serve-the-architecture/</id> <content type="text/html" src="https://topzyray.github.io/posts/express-vs-nestjs-the-framework-should-serve-the-architecture/" /> <author> <name>Tope Taiwo</name> </author> <category term="Backend Engineering" /> <category term="Node.js" /> <summary>Compare Express and NestJS through architecture, constraints, and team needs to choose a framework that fits the system.</summary> </entry> <entry><title>Feature-Based Architecture in Node.js</title><link href="https://topzyray.github.io/posts/feature-based-architecture-in-nodejs/" rel="alternate" type="text/html" title="Feature-Based Architecture in Node.js" /><published>2026-10-09T08:00:00+01:00</published> <updated>2026-10-11T07:53:41+01:00</updated> <id>https://topzyray.github.io/posts/feature-based-architecture-in-nodejs/</id> <content type="text/html" src="https://topzyray.github.io/posts/feature-based-architecture-in-nodejs/" /> <author> <name>Tope Taiwo</name> </author> <category term="Backend Engineering" /> <category term="Architecture" /> <summary>Compare feature-based and layer-based Node.js project structures, and see how organizing code by business capability supports growth.</summary> </entry> </feed>
