May 2026 Summaries

Azion has received recognition in the G2 Summer 2026 Reports across nine categories, including being named a Leader in Content Delivery Network (CDN) and receiving High Performer status in various security and infrastructure categories such as Web Security, Cloud Security, Load Balancing, and DDoS Protection. This recognition highlights Azion's consistent progress, reflecting its ability to deliver fast, reliable experiences while maintaining security and operational control, which is critical for organizations dependent on speed and consistency. Azion's platform is praised for combining performance, security, and control into a unified Web Computing Platform, offering solutions like caching, functions, and built-in protection. The platform's recognition in security categories underscores its capability to address modern threat landscapes with a unified, automated approach, while also supporting traffic management and application protection through features like Web Application Firewall (WAF) and Bot Detection and Mitigation. Customer feedback indicates high satisfaction, with 100% of users expressing confidence in the platform's direction and willingness to recommend it. Azion's role has evolved from being a provider to a strategic partner, delivering consistent, transparent, and effective security and stability solutions that are crucial for growth in scenarios like e-commerce.

The Azion Console faced issues with state coherence, not performance, as it expanded, leading to unnecessary data reloads and context loss. The solution involved rebuilding the Console's data layer to centralize data management, rather than relying on each view to handle its own data loading and synchronization. A BaseService abstraction was introduced to unify data handling processes, enabling consistent cache behavior and synchronization across multiple tabs and sessions. Key architectural choices included hierarchical query keys for predictable invalidation, synchronous cache hydration to improve user experience during transitions, and persistence through IndexedDB with encryption for data security. Cross-tab synchronization was achieved using BroadcastChannel and Server-Sent Events (SSE) to maintain real-time updates without excessive resource use, while a primary tab election system optimized SSE connections. The challenges highlighted that state coherence depends on a structured invalidation architecture rather than merely reducing request frequency, offering a valuable lesson for developers managing complex state dependencies in single-page applications.

Azion has announced a major upgrade to its CLI, significantly speeding up static file uploads during deployments by reducing upload times by 90%, from 1 minute and 35 seconds to between 3.5 and 9 seconds. This improvement is achieved through dynamic worker allocation, which adjusts the number of parallel upload workers based on available CPU cores, enhancing the efficiency and consistency of upload performance on different hardware. The update offers developers the ability to manually set worker numbers via the --workers flag, and provides transparency through a --debug option that reports detailed deployment timing for better troubleshooting. These enhancements position Azion's CLI as faster than many competitors, aiming to improve developer experience by minimizing deployment delays and allowing for quicker innovation and scaling.

Azion is transitioning from a monolithic library model to a distributed monorepo architecture to enhance developer experience, project performance, and sustainability by migrating to individual npm packages. Previously, installing Azion's main package meant receiving a variety of modules and dependencies, leading to larger installations, confusing versioning, unnecessary updates, and inefficient CI/CD processes. With the new structure, each library module is published independently under the @aziontech namespace, allowing for more modular, lightweight, and predictable installations. This change addresses the limitations of the previous model by enabling semantic versioning per package, reducing installation size, isolating dependencies for better security, and streamlining CI/CD processes to focus only on changed packages. The transition to individual packages offers better tree-shaking, smaller bundles, more control over updates, and compatibility with modern monorepo tools, while providing clearer documentation and changelogs for each module. This strategic shift respects developers' choices, aligns with contemporary practices, and aims to deliver a more efficient and scalable development experience for Azion users.