Why “running service” should be part of the data model in your internal developer portal

In the discussion of data models for internal developer portals, the inclusion of a "running service" element is highlighted as a crucial yet often missing component. While traditional software catalogs focus on static data, a running service model tracks live versions of services across various environments, such as development, staging, and production, offering real-time insights into service status, uptime, and other critical metrics. This approach, exemplified by Port's internal developer portal, allows for enhanced functionality within CI/CD workflows by providing detailed metadata about services, environments, and deployment strategies. The running service model, therefore, offers a dynamic layer of information that enriches the software catalog and aids in automated deployment processes, setting it apart from more static catalog models like Spotify's Backstage.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.