December 2023 Summaries

Qovery has introduced a feature that simplifies the deployment of Helm Charts, a critical tool in Kubernetes management, through its web console, CLI, and Terraform Provider, targeting both Platform Engineers and Developers. This enhancement offers several advantages over the traditional Helm CLI, including automated service discovery, ingress configuration, cost reduction through auto-deploy changes, and easy access to pod logs and status. By automating the complex aspects of Helm Chart deployment, Qovery aims to make Kubernetes more accessible without sacrificing flexibility or power, facilitating both quick deployments and complex applications. The update allows for seamless deployment of tools like the Datadog Helm Chart, which previously required extensive manual configuration, by integrating Qovery environment variables and macros to streamline processes. This feature is compatible with Qovery's Bring Your Own Kubernetes option and anticipates further integration with OpenTofu for Terraform module deployment, highlighting Qovery's commitment to enhancing user experience and scalability in Kubernetes management.

Qovery's port-forwarding feature, accessible via its CLI, enables developers to create secure, encrypted tunnels from their local machines to cloud-hosted applications, containers, or managed databases without exposing them to the public internet. This process begins with a port-forwarding request through the Qovery CLI, which works with the Qovery API to establish the tunnel, allowing for secure and direct interaction with remote resources as if they were local. Designed with both security and convenience in mind, this feature enhances the developer experience by mitigating security vulnerabilities associated with public exposure and supports a versatile range of applications. It aligns with Qovery's vision of empowering developers and providing an efficient Internal Developer Platform, with further technical details to be explored in a future article.

In 2024, the developer experience (DX) is set to become a central focus, with efforts aimed at making software building and deployment more intuitive and enjoyable. Platform Engineering is increasingly prioritizing developer empowerment, creating ecosystems that promote autonomy and reduce cognitive overload and context-switching. Internal Developer Platforms (IDPs) are expected to become crucial in tech companies, offering self-service models that enhance efficiency and foster innovation by automating repetitive tasks and standardizing application management. Kubernetes will see advancements to become more user-friendly, abstracting its complexities to broaden accessibility. Additionally, ephemeral environments are predicted to revolutionize development by providing temporary spaces for testing and experimentation, improving development cycles and code quality. These trends represent a cultural shift towards more developer-centric, agile, and efficient software development environments, ultimately driving innovation and accelerating business growth.

Backstage, an open-source framework developed by Spotify, is commonly misunderstood in several ways that can affect its implementation within organizations. Contrary to the belief that it automatically enhances the developer self-service experience, its effectiveness depends on careful customization and ongoing feedback to meet specific organizational needs. It is not a ready-to-use solution out of the box, requiring significant setup and configuration to align with existing workflows. Backstage is not meant to replace existing DevOps tools but to integrate with them, creating a cohesive interface that enhances current workflows. Additionally, it should not be confused with an Internal Developer Platform (IDP); while both aim to improve developer experience, Backstage serves as an Internal Developer Portal that centralizes tools and services without providing a comprehensive suite of development capabilities like an IDP. Understanding these distinctions is crucial for organizations to effectively implement Backstage and leverage its potential in conjunction with their existing processes.

In 2023, Qovery solidified its reputation as a leading cloud infrastructure platform, achieving significant milestones such as exponential growth in deployments, a fourfold increase in revenue, and a tripled customer base. The company was recognized as a Momentum Leader and received its eighth consecutive High Performer award in the Cloud Infrastructure Automation category from G2. Key product enhancements, including job deployments and support for ARM instance types, alongside strategic partnerships with companies like Doppler and Kubecost, enriched the developer experience for over 60,000 users. Looking ahead to 2024, Qovery plans to support GCP and Azure platforms, offer Qovery BYOK for Kubernetes clusters, and further develop open-source tools like Replibyte and Torii. The company aims to triple its customer base, quadruple platform usage, achieve profitability, and strengthen partnerships, while also continuing to engage with the community through industry events.

The text discusses various alternatives to Rancher, a popular container management platform, highlighting the balance each offers between simplicity and control. While Rancher is recognized for its comprehensive features and control, it requires significant operational overhead and expertise, making it more suitable for larger organizations. In contrast, alternatives such as Qovery, Portainer, Platform9, Docker Swarm, and Nomad cater to different needs by offering user-friendly interfaces and specific strengths. Qovery simplifies cloud integration for small to medium-sized businesses, while Portainer enhances Docker and Kubernetes accessibility for smaller teams. Platform9 provides a fully managed service that reduces complexity, Docker Swarm integrates seamlessly with Docker for straightforward orchestration, and Nomad offers flexibility in managing both containerized and non-containerized applications. Each alternative presents a distinct approach to container orchestration, allowing teams to choose based on their size, technical requirements, and desire for ease of use versus advanced features.

The text discusses the complexities and common pitfalls associated with asynchronous programming in Rust, focusing on issues such as task cancellation, the misuse of mutex types, and the challenges of future progress starvation. It highlights how tasks can be unexpectedly canceled or stopped, leading to complications like incomplete task counters and the inefficient recreation of futures in loops, which can be mitigated by using constructs like `scopeguard` and `fuse`. The document also warns against holding resources across `await` points, which can cause deadlocks, and suggests early dropping of such resources to prevent them. Furthermore, it critiques the overuse of async programming when traditional synchronous methods could suffice, stressing the increased complexity and debugging difficulties that async introduces. The text concludes by advocating for a balanced approach to async use, treating it as a library rather than the core architecture, to maintain code simplicity and improve team adaptability.

Internal Developer Portals like Backstage are highly beneficial for large-scale organizations with extensive engineering teams due to their ability to manage complex tech landscapes, but they may be overwhelming for smaller teams that prioritize agility and simplicity. Smaller teams often benefit more from streamlined Internal Developer Platforms such as Qovery, which offer a self-service experience without the complexity Backstage entails. A significant barrier to adopting Backstage is the need for substantial frontend development skills, particularly in React, which poses challenges for teams whose expertise lies in backend development, infrastructure, or DevOps. Additionally, Backstage requires a long-term commitment to setup and maintenance, making it resource-intensive and potentially burdensome for smaller organizations. Ultimately, while Backstage suits large organizations with complex needs, smaller teams might find more practical benefits in platforms that focus on core development workflows and ease of use.

Platform as a Service (PaaS), such as Qovery and Rancher, provides a comprehensive environment for app development, abstracting infrastructure to simplify deployment on cloud platforms like AWS and Google Cloud. It integrates development tools and middleware, allowing developers to focus on application creation rather than underlying infrastructure. Managed Kubernetes services, including Amazon EKS, Google GKE, and Microsoft AKS, automate the setup, scaling, and maintenance of Kubernetes clusters, integrating deeply with respective cloud ecosystems to offer scalability and high availability while reducing the need for specialized expertise. Container as a Service (CaaS) like VMware Tanzu provides robust management tools for container orchestration, ideal for enterprises needing control over their container environments. Meanwhile, tools like Nomad by HashiCorp offer a more straightforward and flexible orchestration option for mixed workloads. Each of these solutions varies in ease of use, scalability, security, and cost, making the choice dependent on specific organizational needs and existing infrastructure investment.

Self-service access within Internal Developer Platforms (IDPs) significantly enhances developer experience by granting autonomy and efficiency, allowing developers to independently manage resources and integrate seamlessly with DevOps practices using tools like Kubernetes and AWS. GitOps, a paradigm using Git repositories as the source of truth, automates infrastructure provisioning and management, ensuring consistent and reproducible deployments while enhancing collaboration and security. Schema management in IDPs provides a foundational framework for consistent data structures and integrity, crucial for applications like fintech platforms, while automated testing and CI/CD pipelines ensure software quality and accelerate release cycles by integrating with various development tools. Comprehensive monitoring and observability in IDPs enable proactive performance management and issue resolution, akin to healthcare diagnostics, while Role-Based Access Control (RBAC) secures the environment by assigning access based on roles, preventing unauthorized access and ensuring compliance. Together, these components enable organizations to optimize developer productivity, streamline processes, and drive innovation through the effective implementation of an IDP.

Internal Developer Platforms (IDPs) are becoming a crucial part of modern IT infrastructure, streamlining software development processes by integrating development, operations, and cloud technologies. This guide outlines a strategic approach for CTOs to adopt IDPs, starting with understanding their significance, conducting a needs analysis, and developing an implementation plan. Key steps include ensuring team buy-in, continuous monitoring, and adaptation to evolving business goals. Organizations must assess their current infrastructure, team readiness, and budget implications before implementation. Forming a dedicated platform engineering team and promoting cross-department collaboration are critical to success. Best practices for building an effective IDP include focusing on user needs, integrating existing tools, ensuring simplicity, automating processes, and considering scalability. Security, compliance, monitoring, and continuous improvement are emphasized as essential components. IDPs enhance developer experience by automating routine tasks, standardizing environments, and improving team collaboration. Challenges such as integration complexity, scalability, and security must be addressed, but the opportunities for faster development cycles, advanced automation, and cloud-native solutions make IDPs a strategic asset for future-ready businesses.

Qovery developed the IAM EKS User Mapper to simplify and enhance the security of handling Kubernetes cluster access, addressing the challenges of manual management. Built using Rust for its superior performance and reliability, this tool automates the synchronization of IAM users within groups into the Kubernetes cluster's aws-auth configmap and supports SSO roles, streamlining secure access management. By open-sourcing the tool, Qovery invites community participation for improvements and feedback, encouraging contributions through platforms like Reddit and GitHub. This initiative aims to reduce the complexity and increase the security of Kubernetes management, fostering a collaborative approach to refining access management solutions.