Internal Service Marketplace

⭐️🏒 CoreTeams offer services to other teams and make them accessible on a marketplace that is integrated with πŸ’΅ Cost Management and πŸ” IAM .

🚧 This building block reference page is a draft.

If you want to be notified when the building block reference page is finished, click here.

Cloud is a way to deliver IT that maximizes business outcomes. Where classical IT services meant opening tickets or writing emails to 10 different stakeholders, the cloud is about having a single interface for DevOps teams to get everything they need to be productive. An internal service marketplace is a crucial part of getting away from a classical IT service operating model.

By providing a standardized interface, an internal marketplace enables platform teamsopen in new window to provide their services with minimal friction, thus reducing the cognitive overhead for consuming teams and platform teams alike.

How to Make an Internal Service Marketplace Successful

Treat the Internal Service Marketplace like a Cloud Platform

Integrate the marketplace into the Cloud Foundation offering as if it were its own cloud platform. This allows service owners to build upon everything already provided by the Cloud Foundation Platform, especially for

Notice that Cloud Providers offer marketplaces on their control planes as well: AWS Service Catalogopen in new window, GCP Service Catalogopen in new window, and Azure Marketplaceopen in new window. Those are examples of services integrated with the providers control plane and hence inherit all the CFMM pillar functionality from the cloud.

Make Services Easily Discoverable

Making the complete service portfolio as easily discoverable as possible, makes it more likely that customers can choose the best solution for the job. Ideally, teams only needs access to the Cloud Foundation Platform to explore the options available to them.

Guide Platform Teams to Offer Their Services

Starting out with the Internal Service Marketplace, the Cloud Foundation team will most likely only provide its own services a a part of a Modular Landing Zones approach. Later in the cloud journey, platform teams will need to offer their services on the Internal Service Marketplace to gain the benefits of discoverability and standardization.

Effectively, the Cloud Foundation team offers the marketplace as a platform to other platform teams.

Use a Single Marketplace for All internal services

This follows from the above points. If there is a single entry point, the cognitive overhead for teams is reduced. No more β€œwhere could I find service x?” by users or β€œWhere should we offer our service?” by platform teams.

While internal services should only be offered on a single internal service marketplace, services that are available on platform native marketplaces like the Azure Marketplaceopen in new window should not be encapsulated, but managed via these platform native marketplaces instead, if their usage is compliant.

Choosing a marketplace independent from a third party marketplace means fewer technological restrictions: For example, you are not bound to using Azure ARM only, or AWS Cloud Formation. Instead you can use tooling like terraform.

When choosing a single marketplace for internal services, the ease to incorporate internal IT infrastructure needs to be a key consideration. DevOps Teams moving to the cloud in a β€œhybrid” setting need internal services like IPAM, SSL certs, internal DNS etc.

Make Use of Synergies When Implementing Services

Some services need to integrate with a cloud tenant. Those integrations necessarily are platform specific.

Two example services, that need to integrate with a cloud tenant:

Integrating those services for multiple platforms necessarily means building platform specific code. However, some parts can and should be reused when implementing services.

For the two example services above, these parts could be modularized and shared across cloud platforms:

To allow modularization, use tooling that is not cloud platform specific for those services. Terraform has been a solid choice for many teams in the past.

  • meshStack

    Every Cloud Foundation customer can offer services on the meshStack marketplace to other teams in your enterprise.

    Learn More open in new window
Last Updated: