July 2024 Summaries

Financial services company, Company Z, has improved its onboarding process and team fluidity by implementing automated development environments using Gitpod. This has allowed the company to standardize environments across varying operating systems (Windows, Mac, Linux), reducing environment drift and reproducibility issues. The adoption of Gitpod's "self-hosted, but not self-managed" infrastructure has also eliminated operational overhead for Company Z, which had limited DevOps engineering capacity. By automating development environment setup, the company has been able to improve onboarding speed and eliminate operating system incompatibility issues, enhancing overall business agility.

Amazon Web Services (AWS) has decided to close new customer access to its Cloud9 service as of July 25th, 2024. AWS will continue to invest in security, availability, and performance improvements for existing customers but will not introduce any new features. This move impacts services that rely on Cloud9 such as CodeCatalyst. As a result, customers are looking for alternatives. One potential solution is Gitpod, which offers self-hosted enterprise-grade development environments integrated with AWS. Gartner predicts by 2026, 60% of cloud workloads will be built and deployed using solutions like Gitpod.

A leading insurance provider has improved developer productivity by transitioning to secure, standardized, and automated development environments using Gitpod Enterprise. The company previously faced challenges with inefficient VDI setups on Windows machines, compatibility issues, and long lead times for special high-powered environments. By decoupling software development from desktop use cases and aligning development environments with production based on Linux, the insurance provider has enhanced developer experience while maintaining strict regulatory and compliance requirements. The adoption of Gitpod has also enabled platform teams to define development environments in declarative configuration and empowered developers with improved flexibility and control over tooling installation.

Developing inside a Docker container involves setting up your development environment within a containerized environment, providing consistent and reproducible environments across different systems. This approach offers benefits such as simplified set up and onboarding, isolation, and portability, making it particularly useful for complex projects, cross-platform development, or collaborative environments. However, there are certain situations where developing inside a Docker container may not be the most suitable approach, such as simple or lightweight projects, limited resources, specific hardware or system dependencies, or incompatible tools or plugins. To get started with developing inside a Docker container, choose a base image, create a Dockerfile, build the Docker image, run the Docker container, and optimize for performance. Additionally, leverage multi-stage builds, develop inside the container, and use Docker Compose for more complex setups involving multiple containers.

Venv and Conda are two popular tools for creating isolated Python environments to manage dependencies and maintain consistent development and production environments. Venv is a module that comes preinstalled with Python 3.3 and later, while Conda is an open-source package and environment management system that supports multiple programming languages. Both tools have their strengths and weaknesses, making them suitable for different project requirements. Venv is ideal for simple, Python-only projects, whereas Conda excels at managing complex dependencies across multiple languages. By understanding the differences between these tools, developers can make an informed decision and set up their projects for success.

Company Z, a financial technology company specializing in personal loans and credit products, managed to streamline its development processes by adopting Gitpod's cloud development environment (CDE) through Ona, leveraging AWS infrastructure. This transition was driven by challenges such as technology sprawl and operating system disparities, which hindered developer productivity and onboarding. The standardization facilitated by Gitpod allowed for quicker onboarding and reduced environment drift, enabling developers to work fluidly across various tech stacks and operating systems, thus supporting the company's rapid growth and diversified product strategy. By using a CloudFormation template, Company Z efficiently deployed Ona's architecture, including VPCs, EKS clusters, and RDS databases, within a day, eliminating operational overhead and ensuring a seamless setup of standardized development environments. This approach not only improved business agility but also mitigated risks associated with knowledge silos and hardware compatibility issues.

Company 'Y', a leading provider of insurance solutions, transitioned to Ona Enterprise to enhance the security and efficiency of their development environments, replacing their previous Virtual Desktop Infrastructure (VDI) setup with Citrix. This move allowed them to overcome the limitations of developing on underpowered Windows machines by adopting Ona’s Linux-based standardized development environments, which align better with their production systems. The switch to Ona provided 'Y' with the flexibility to create ephemeral and resource-efficient development environments, significantly reducing environment drift and improving developer experience by balancing compliance requirements with developer autonomy. By decoupling software development from desktop use cases, developers could work more efficiently without compromising the performance of administrative applications. Additionally, 'Y' implemented a secure, private networking configuration for Ona, ensuring control over identity and access through integration with their GitLab repository. The automation and ease of updates with Ona's system further streamlined their operations, providing continuous product enhancements and cost optimizations without significant downtime.

Gitpod has been named an IDC Innovator for Cloud Development Environments (CDEs) in 2024. The recognition comes from the company's dedication to improving developer experience and its innovative self-hosted, not self-managed deployment model. Key areas where Gitpod stands out include developer experience, security, and cost controls. The company's centralized security approach gives platform teams granular control over access to environments, while automation enables temporary and specific data access permissions. Additionally, the self-hosted, vendor-managed deployment eliminates day 2 operational overhead, ensuring all security and compliance controls are in place.

Founded in 2020, Gitpod has emerged as a leader in the cloud development environment (CDE) industry, as recognized by IDC in their 2024 Innovators report. Gitpod is praised for enhancing developer experience, boosting security, and implementing cost controls, which are crucial to its customers. It simplifies project onboarding and developer productivity by making the setup process straightforward, whether for new hires or remote contractors. Gitpod's centralized security model allows precise control over environment access, ensuring data security through OpenID Connect and flexible deployment models, including air-gapped deployments. Cost efficiency is achieved through a self-hosted, vendor-managed deployment approach, eliminating operational overhead and providing security and compliance control within customer cloud accounts. The IDC Innovators study highlights the role of CDEs in transitioning organizations from local development to cloud-based platforms, emphasizing productivity and a seamless developer experience.