What’s up with internal developer portals? | Chris Westerhold (Thoughtworks)
Apr 9, 2024
auto_awesome
Thoughtworks Head of Developer Experience, Chris Westerhold, discusses the rising interest in developer portals, pitfalls to avoid, building vs. buying, driving value, and common mistakes. Explore the evolution of internal developer portals and strategies for optimizing success in this insightful conversation.
The rising interest in developer portals is driven by the need to simplify access to tools amid complex engineering ecosystems.
Successful developer portal projects require a product mindset, focusing on quick value demonstration and iterative improvements based on user feedback.
Deep dives
Rising Interest in Developer Portals and Trend Drivers
The rising interest in developer portals stems from the increasing complexity in engineering organizations due to factors like shifting to the cloud, adopting multi-cloud environments, and managing distributed architectures. The main driver behind this trend is navigating the complex ecosystem for software developers to access the tools they need efficiently amid the influx of technologies like microservices and serverless functions. Innovations in tooling within the microservices and data spaces further emphasize the need for simplifying access to resources.
Understanding Internal Developer Portals vs. Platforms
Internal developer portals and platforms serve as unified interfaces for developers, centralizing tools and resources within organizations. While developer portals focus on creating a seamless user experience through features like catalog search and self-service options, platforms emphasize orchestration and interaction functionalities. The convergence of these two concepts envisions a consolidated approach that streamlines developer interactions with technology resources, leading to enhanced developer experiences across varied tasks and tools.
Building vs. Buying Developer Portals: Considerations and Challenges
Organizations face decisions regarding building or purchasing developer portals, with each option presenting distinct advantages and challenges. Building offers flexibility in tailoring solutions to specific needs but requires ongoing maintenance and scalability. Conversely, buying solutions provide quick implementation and established features, yet necessitate alignment with existing processes and potential limitations in customization. Understanding organizational goals, resource allocation, and desired outcomes are essential in determining the most suitable approach for effective developer portal implementation.
Driving Success in Developer Portal Initiatives: Product Mindset and Continuous Improvement
Successful developer portal projects demand a cohesive approach integrating technology, process improvement, and user engagement. Embracing a product mindset involves treating developer portals as startups within organizations, focusing on demonstrating quick value, securing funding, and ensuring ongoing momentum. Prioritizing problem-solving and iterative enhancements based on user feedback fosters cultural change and drives continuous improvement. Implementing a methodical and community-oriented strategy rather than imposing changes accelerates success and fosters productive developer interactions and experiences within organizations.
This week’s episode is the recording of a live conversation between Abi and Chris Westerhold (Thoughtworks Head of Developer Experience). This conversation is useful for anyone early in their journey with developer portals or platforms: Abi and Chris discuss common approaches to solving these problems, pitfalls to avoid, building vs. buying, and more.