I'm a full-stack developer and security researcher who loves digging into internals, simplifying complex systems, and building tools that help developers move faster.
- Think in terms of architecture and edge cases
- Explore platform internals (like Atlassian Forge)
- Build and optimize developer tools
- Research and report security vulnerabilities in developer platforms
An architectural approach for integrating external services into Atlassian Forge apps without breaking the “Runs on Atlassian” model.
The pattern uses route.navigate and static web triggers to enable inbound-only communication, ensuring all execution remains inside Atlassian’s trusted environment.
It was confirmed by Atlassian Staff as fully aligned with Forge’s design principles.
📘 Read the discussion: ➡️ Integrating External Services in Atlassian Forge
🧠 Implementation demo: ➡️ Forge Health Monitor
A gateway layer built on top of Keycloak for protecting and serving static or dynamic resources in multi-tenant environments.
It provides a role-based access control layer for JavaScript bundles, APIs, and files, working across Express, Lambda@Edge, and serverless deployments.
Supports realm- and tenant-based routing, dynamic resource mapping, and pluggable storage backends (InMemory, DynamoDB, etc.).
📘 Project: ➡️ keycloak-api-gateway
🧩 Examples:
📘 Published on the Atlassian Developer Blog
- Optimizing Forge SQL on a 600K+ Database with TiDB EXPLAIN A deep dive into query performance, execution plans, and how to work with large datasets in Forge SQL — based on real experiments and analysis.
- How to Prevent Data Loss in Forge SQL: Optimistic Locking in Action How to use optimistic locking in Forge SQL to prevent data loss with concurrent updates.
📰 More articles on Dev.to: ➡️ @vzakharchenko
- GitHub: @vzakharchenko
- Dev.to: vzakharchenko