March 2023 Summaries

Unleash 4.22 introduces several new features aimed at enhancing collaboration and control over feature management. The update includes a maintenance mode that allows administrators to temporarily restrict changes to configuration settings and APIs, ensuring tighter control during critical situations, while still permitting read access to configurations and normal functioning of SDKs, proxies, and Edge. The addition of collaboration modes lets users customize change request permissions, offering an open mode for all users and a protected mode restricted to admins and project members. The environment export/import functionality simplifies moving feature flags between instances or environments while preserving configurations, facilitating seamless transitions, such as migrating from open-source to Enterprise versions. Pro and Enterprise users benefit from a new notification system, providing alerts on events like change requests and feature management actions. The release also includes features in beta and project-level access tokens, with further details available in the release notes.

Unleash has introduced a Community Content Program inviting members of its community with expertise in DevOps, software delivery, or Unleash setup to contribute articles to its company blog. Participants are encouraged to share their experiences with feature flags and the challenges they face as developers, offering a platform to publish their insights and enhance their visibility. Contributors will receive a flat rate of $200 USD per submission, with no limit to the number of submissions. Interested individuals can register by filling out a Google Form, join the Community Content Program on Slack, and receive feedback on their topic suggestions within a week. The program aims to leverage the knowledge and writing skills of the community to enrich the blog and provide valuable content to a wider audience.

Unleash's new Edge platform marks a significant evolution from its predecessor, the Unleash proxy, by offering a faster, lighter, and more resilient solution that integrates seamlessly with both front end and back end applications. Edge simplifies the infrastructure by allowing all environments to be housed in a single instance, reducing the cost and complexity associated with running multiple instances of the proxy. Unlike the Unleash proxy, Edge operates as a read replica of Unleash, which enhances scalability and cost-efficiency, and it can function independently of an upstream Unleash server after initial connection, ensuring continuity even if the server goes down. This design philosophy not only improves performance by using significantly fewer resources but also enhances resilience and user experience, making it easier to manage and maintain. Future developments are focused on improving connectivity and providing detailed insights into the health of connected SDKs, with ongoing feedback and collaboration encouraged from users to refine and expand its capabilities.

Unleash has introduced a new strategy for enhancing the resilience of its Java SDK by bootstrapping it with predefined values, a feature available from version 4.2.1. This method allows the SDK to function independently of a network connection by loading feature flag configurations from predefined values at startup, which is beneficial when network access to the Unleash server is unavailable. The process involves using backup files stored either on disk or in the application's classpath, and developers can also configure the SDK to load from AWS S3 by implementing a custom provider. The bootstrapping approach ensures that the application can maintain a consistent feature flag state, even in environments where permanent storage is inaccessible, such as in containers. This new feature is part of a broader commitment to improve the robustness and reliability of feature management systems.

Scaling up smartly in 2023 involves expanding infrastructure and applications efficiently while minimizing risks and costs. This process is crucial for DevOps teams to handle increased traffic and workloads, ensuring organizations remain competitive. Smart scaling focuses on data-driven decisions, optimizing resource allocation, and enhancing team cooperation and communication. To mitigate risks and improve efficiency, teams should automate processes using tools like continuous integration and deployment (CI/CD), while prioritizing safety through security measures such as encryption and multi-factor authentication. In regulated industries, compliance with data privacy standards is essential, requiring automation of security processes and fostering a culture of security awareness. Planning for successful scaling includes setting clear goals, evaluating infrastructure, optimizing development processes, and investing in quality assurance. Flexibility and adaptability are key, as monitoring and adjusting systems ensure a smooth scaling journey, ultimately allowing businesses to thrive and seize new opportunities.

Platform engineering has emerged as a significant trend within the DevOps landscape, focusing on creating internal developer platforms that reduce cognitive load and empower developers to efficiently own and operate their services without needing to become DevOps experts. Unlike traditional DevOps or SRE teams that often manage operational tasks, platform engineering provides a user-friendly abstraction over complex tools and processes, enabling developers to focus more on application development rather than operational minutiae. This approach utilizes "golden paths," which are standardized pipelines that streamline code deployment and reduce repetitive operational toil, enhancing productivity and reducing error-prone manual work. Platforms are treated as internal products, continuously refined based on developer feedback and metrics like DORA, to ensure they meet the evolving needs of engineering teams. Unleash, as an open-source API-first tool, can seamlessly integrate into these platforms, aiding in feature toggling during deployments. While smaller organizations might wait until reaching a certain size to invest in platform engineering, established companies with existing DevOps cultures can benefit from productizing their internal services to alleviate developer pain points and enhance operational efficiency.

In the evolving landscape of software development, separating feature releases from deployments has become crucial for high-performing DevOps teams, as highlighted by Egil Østhus. Historically, bundling multiple features in a single deployment was common, but this approach often led to inefficiencies. High-performing DevOps teams, as discussed in the book "Accelerate," are characterized by frequent deployments, allowing for faster feedback and shorter implementation times. However, excessive deployments can pose challenges, such as using live environments as testbeds, which can impact user experience and marketing strategies. Feature flags offer a solution by decoupling production deployment from feature release, enabling controlled rollouts and better management of user access, thus enhancing testing and user feedback. Tools like Unleash facilitate this process by allowing teams to manage deployments strategically, aligning with business objectives and ensuring a positive user experience while maintaining a competitive edge.

Deployment frequency, a key DORA metric, measures how often an engineering team deploys code to production and is crucial for obtaining early customer feedback, guiding product development in the right direction. High-performing organizations deploy multiple times a day, enabling them to be more agile and responsive to change. Early feedback mechanisms, like test-driven development and continuous integration pipelines, encourage frequent testing and rewriting of code to catch faults early, making small, incremental releases easier to manage and revert if necessary. However, merely increasing deployment frequency without maintaining code quality can be counterproductive. Effective deployment frequency should stem from robust engineering practices, including a strong CI/CD pipeline, minimizing change sizes for simpler code reviews and faster bug isolation, and fostering a culture of ownership and collaboration across teams. While deployment frequency is not a cure-all, it serves as an important indicator of engineering effectiveness, supporting a culture that prioritizes automation, quality, and the ability to learn from iterative changes.

Egil Østhus discusses the advantages of self-hosted feature management with Unleash, emphasizing flexibility, security, privacy, GDPR compliance, reliability, and cost-effectiveness as key reasons to consider this option over cloud-based solutions. Self-hosted systems allow organizations to maintain complete control over their data and infrastructure, reducing the risks associated with multi-tenant environments and external access to sensitive information. Unleash's architecture supports this approach with its API-first strategy and event-driven model, enabling seamless integration into unique workflows. However, self-hosting requires teams to manage their deployments, including service stability and security, which may not be ideal for businesses that prefer to focus on their core products and outsource non-strategic tasks.

Unleash 4.21 introduces several enhancements centered on fine-grained control, particularly through environment-dependent variants, which allow modifications specific to certain environments without affecting others, thereby facilitating more precise access control and integration of change requests. The update also includes UI improvements, such as the ability to check active variants by hovering, and features like pushing and copying variants between environments, eliminating migration concerns for existing projects. Additionally, users can now monitor Unleash API traffic directly via an overview tab, and enterprise users benefit from the introduction of service accounts, which provide more detailed permissions for integrations than traditional admin tokens. Unleash 4.20's feature to pin favorite feature flags for easier sorting is also highlighted, with all new features detailed in the release notes.