Recommended
Recommended
More Related Content
Similar to Anypoint Exchange: It’s Not Just a Repo!
Similar to Anypoint Exchange: It’s Not Just a Repo! (20)
Recently uploaded
Recently uploaded (20)
Anypoint Exchange: It’s Not Just a Repo!
- 1. Anypoint Exchange PM: Ria Joshi
- 2. Goodmorning!
- 3. Agenda Section 1 Overview of Anypoint Exchange Section 2 Network Effects due to Reusability Section 3 Asset Engagement and Usage Metrics
- 4. Exchange is a repository for APIs, automation, and integration resources What is Exchange About Anypoint Exchange is a marketplace and repository for APIs, automation, and integration resources. It integrates seamlessly in your flow of work and provides capabilities to discover, produce, and consume reusable assets which helps jumpstart your developer journey. Key Benefits - Reuse assets to jumpstart development journey - Understand detailed version information - Governance and lifecycle management - Mocking service and testing - 28 asset types supported
- 5. Let’s watch a quick video with some more information
- 6. Find and consume assets to meet my needs Anypoint Exchange A marketplace of reusable assets - a unique differentiator CATALOG CONSUMPTION Consumer Producer Value Exchange Anypoint Exchange Platform Build valuable assets and share with consumers Customer created + MuleSoft provided assets Exchange Studio Flow Designer API Designer API Manager Runtime Manager API Community Manager
- 7. Just scratching the surface... Opportunity to deliver massive value CATALOG (Deeper & Wider catalog of reusable building blocks) Storage Versioning Metadata Search Publication Consumption More asset types Richer metadata for entire lifecycle of assets Wider sources of assets Governance & reporting Tailored developer journeys to increase reuse Metadata based recommendations Cut down time to learn & adopt
- 8. Key Customer Personas + Use cases Who does Anypoint Exchange serve? As a Developer (Consumer) I discover, engage and consume assets on Exchange to test, download, share or reuse an asset for my development. As an Exchange admin, I am involved in publishing content to my org portals. This helps ensure that all assets are of high quality and value, are in the proper lifecycle state, and assets that are ‘stale’ are deleted or deprecated. Production of Assets Consumption of Assets As a Developer (Publisher) I create assets and publish them to Exchange. My goal is to implement and deploy reusable building blocks or solutions available for other developers to teams. As the Marketplace and Application network owner I am responsible for the governance and efficacy of the application network via Exchange. I want to be able to identify top adopted assets, so that I can promote best practices & assets across the catalog
- 9. User Journeys Supported Anypoint Code Builder AEH Internal
- 10. Content on Exchange APIs ● API Groups ● API Spec Fragments ● REST APIs ● RAML ● OAS ● SOAP APIs ● GraphQL APIs ● AsyncAPI Specs ● HTTP APIs ● Custom Integration ● Connectors ● Examples ● Templates ● Policies ● Rulesets ● DataWeave Libraries ● Mule Applications Automation ● RPA Activity Templates ● RPA Process Templates
- 11. What are customers saying about reuse? “My organization has keen interest in tracking re-use of our Mulesoft-based assets, both of APIs and of the API Spec Fragments. I understand what is required to set-up APIs for re-use (client_id & secret policy, Mule "Application" per potential invoking client) and the subsequent derivation of this information.” – MuleSoft Customer “Where API Spec Fragments are concerned, I think it [reuse] would be a great enhancement in order to measure the KPI of reusability of the platform if the Exchange Experience API included this where-used capability. I realize I can interrogate every API asset and iterate through them looking for included Exchange fragments, but this seems like a fundamental capability that could be exposed for simpler consumption.” – MuleSoft Customer
- 12. Definition of Reuse “An application development methodology that catalogs and makes available application components so that they may be incorporated into other applications.” – Gartner “Application reuse: An application can be reused by integrating without change into a system or re- configured for a specific customer.” – Dwarves Foundation “Reusability… the ability of something to be used more than once … Reuse… the action of using something more than once …” – Hitachi Group
- 13. Examples in various industries Online communities – engagement actions include # of postings, # of interactions Marketplaces – engagement actions include # of purchases made, # of recommendations, # of product / inventory updates, # of uploads, # of downloads Social Networks – engagement actions include # of shares, # of views, # of likes / dislikes, # of comments Identify what it means for a user to ‘actively engage’ In Principle…. Define relative importance of engagement actions Monitor engagement with each relevant action Develop algorithm to reflect aggregate engagement Deliver insights to users
- 14. Benefits of reusability A key differentiator that helps reduce time to market Jumpstart Development ● Hundreds of connectors and pre-built templates ● Build with MuleSoft ecosystem Reduce Time to Market ● Centralized hub for discovery & reuse ● Breakdown development silos ● Enforce standards & security ● Provide asset usage data to admins & asset owners ● Help admins better manage their organization with best practices Close the Feedback Loop
- 15. Let's take a look at the new Exchange feature which captures reuse and engagement
- 16. New Anypoint Exchange feature offers new insights into your assets’ performance [Released: July 2023) Drive growth, engagement, and reuse across the entire catalog Access usage metrics and engagement scores to get a composite view into how your assets are being utilized Track and manage asset adoption with out-of-the-box dashboards View performance analytics of your entire asset library in a single location Leverage engagement scores to make data-driven decisions
- 17. View Version Level Information You can view engagement rates for specific asset versions. This can help you understand the performance and stickiness of specific asset versions within your organization and enable you to make informed decisions about reuse and improvements. Understand how specific API versions contribute to overall engagement and reuse
- 18. Upcoming Release: Metrics for Connectors, Examples, and Templates [FY25) ● Engagement metrics for 3 new asset types (Connectors, Examples, and Templates) will be available this year ● Use this data to better understand reuse and engagement of your integration assets ● Improve asset quality and Exchange organization housekeeping based on this data
- 19. How can you use this information to better manage your catalog and drive value to end-consumers? Understand engagement of assets in your catalog with the new feature Add asset name + icon to make it easily discoverable Ensure asset is well documented so users understand how to use it + its value Add asset metadata (tags, categories, custom fields) to better classify asset and help users understand value Keep asset versions updated by lifecycle state; deprecate stale versions Encourage users to engage by applying governance states Maintain catalog hygiene by deprecating / deleting stale assets as identified via engagement metrics dashboard
- 20. What’s coming in FY25 Exchange Upcoming Roadmap ● Usage Metrics for Connectors, Examples, and Templates (H1, 2024) ● Enhanced Engagement Score calculator (H1, 2024) ● In-Product Recommendations (H2, 2024) ● Client Application Owner Management (H1, 2024) ● Deprecate Legacy Search (H2, 2024)
- 21. Java 17 Connector Compatibility (February 2024) What was recently released ● Enhanced Connector Asset metadata with Java compatibility details ● Ability to discover Java 17 compliant connectors in Studio and Anypoint Code Builder ● View Java compatibility in Asset (Connector) version details page
- 22. Custom Fields Filter (November 2023) What was recently released ● Custom fields are custom data types created by Exchange Admins using the Exchange API to extend the Exchange asset metadata model ● Assets can be filtered by new custom fields filter to refine a search using preset information. The custom field filter is available only when assets in your organization have custom fields
- 23. Please reach out to riajoshi@salesforce.com Let’s stay in touch! Feedback is always welcome.
- 24. Thank you
Editor's Notes
- Hello hello! I’m looking forward to spending the next chunk of time talking to you about Anypoint Exchange. My name is Ria Joshi and I am currently the product manager for Exchange. I’ve been working on the product for just about 3 years now.
- Let’s begin with a quick video that will set the stage for today’s conversation. [Play video] 12:57 The power of network effects is largely realized in the world of APIs and application networks. In essence, this is the core value of an API. APIs provide ways for users to connect with and access data from systems that we may not have even been aware of prior to this connection. One question we ask ourselves then is “what is a useful set of assets that will allow others to build new things with? And how can I access and perhaps provide these valuable set of assets”? This hits on the concept of reusability. When you identify these sets of assets that have useful capabilities, you want to be able to use them across various business cases. You want to move faster. This is when you realize the true value of these assets and asset catalogs, like Anypoint Exchange and its offerings. With that in mind, let’s move forward and talk more about Anypoint Exchange in the context of reusability and network effects.
- This will be our agenda for the rest of today’s session. We’ll walk through Anypoint Exchange and highlight the key value proposition, different personas and use cases the product serves. Then we’ll circle back to the concept of reusability and take a more detailed look at the value reuse provides with regards to application network effects. And finally we’ll do a deep dive into the Exchange feature which hits on this value.
- With that, let’s dive into an overview of the product. Anypoint Exchange is a marketplace for digital assets that integrates into your flow of work and helps you discover, produce, and consume reusable assets to accelerate your developer journey. We support over 25 types of reusable assets, including various forms of APIs (REST, GraphQL, Async), automation resources (RPA assets), and integration assets such as connectors and templates. Exchange sits at the center of Anypoint Platform, and complements other capabilities within the broader MuleSoft ecosystem by providing a centralized hub for discovering, sharing, and reusing assets. It integrates seamlessly with Anypoint Code Builder / API Studio for development, Anypoint Design Center for API Design, and the runtime management services for deployment. You can interact with Exchange through API Manager to view and manage your APIs and instances, as well as with Monitoring and Governance for performance and conformance status insights. This streamlines the entire integration lifecycle from design to deployment to monitoring.
- Let’s take a look at this spotlight video which overviews Exchange. Stop at 2:37
- As mentioned in the video, Anypoint Exchange today serves as the marketplace of reusable assets. It starts with a simple catalog of MS provided assets that customers can readily use to jumpstart their integrations. As we saw in the video, there’s really two core sides to the Exchange narrative: publication and consumption. As developers build their integrations, more assets become available for other developers or consumers to discover, learn and use. This creates a virtuous cycle of exchange between the producer and consumer, resulting in savings through reuse and boosting innovation through ideas. To break it down a bit further, Anypoint Exchange’s capabilities can be grouped into three main categories. The first area of investment is Asset Production. You can publish assets via various sources to Anypoint Exchange. Most common ways to do this are using maven, the Exchange API, or directly through the Exchange UI. Once published, you can enhance the quality of the asset by adding metadata including documentation, tags / categories / custom fields, as well as manage the lifecycle state and conformance status of the asset. Second, we have Asset Consumption capabilities. The consumption journey begins at the search and discovery phase. If you are logged into Anypoint Exchange, you can intuitively search for assets in your catalog by browsing through the homepage, applying filters, or entering specific search queries. From here, you can navigate to the asset portal page of an asset and test it using the mocking service, download it, or share it with other users in your organization. You can also import assets from Exchange in Studio, API Designer, or Anypoint Code Builder to further accelerate the journey. Finally, we have platform level capabilities. These are capabilities for internal to MuleSoft users, however provide value to developers by 1) enabling the support of a diverse set of asset types and 2) providing coherent and consistent UI experiences across the platform.
- And we’re just scratching the surface with those capabilities. Publication and consumption sits at the first level of interaction with Exchange. As we dive deeper, capabilities such as asset storage, access management, discoverability, and search help users better utilize the offered capabilities. We have a mature search engine implementation to help you quickly and easily find the assets you are looking for, as well as find assets that may be highly relevant to your workflow to jumpstart your development. The asset details page helps you learn more about the asset and how to use it, as well as the different versions and their unique functionality. Other key features include governance, approval workflows, asset monitoring, seamless publication processes, and more. The catalog is continuously scaling, thus providing developers with a rich and diverse set of supported asset types.
- Exchange’s capabilities are tailored towards 4 specific personas, broken down by the production and consumption side of things. On both sides we have a developer and an admin. On the production side, we have: The developer is focused on publishing assets and creating reusable building blocks for other teams. This user is actively involved in creating the asset, whether it be from the Exchange UI or from other sources. The production side Admin is involved in the management, housekeeping, and quality of assets in his or her organization. They care about the quality of assets and want to ensure that each asset produced is up to the organization’s standards so that the end-consumer can easily find and use the asset. On the consumption side, we again have the The developer is the user who will using the asset. They may do this by downloading, testing, or sharing the asset. Additionally, this user is likely reusing these APIs in his or her workflows. The marketplace Admin on this side of the spectrum wants to identify top engaged with assets to promote best practices. Within each user, there are different permission sets that can be allocated. This will help the admin curate the level of access each user in the organization has, which thus dictates the types of actions the user can take within the catalog.
- Exchange assets are accessible from many places, such as Anypoint Studio (connectors, templates, and examples), API Manager (APIs, API groups, and policies), or Runtime Manager (applications). APIs can also be published from Design Center to Exchange. This high level architecture diagram helps better contextualize Exchange with regards to the rest of Anypoint Platform. It also highlights the key user journeys that are supported and frequented by developers. On the production side, developers publish assets to Exchange from 4 key sources: Exchange UI Studio API Designer Anypoint Code Builder (new IDE) These assets are published through various sources: Exchange API, directly from the UI of API Designer or Exchange, or using the maven-facade interface. Assets can be managed via the Anypoint command line interface, anypoint experience hub, API Manager for specs, and the runtime services help with efficient deployment. Each of these products and tools has a way of interacting with the exchange catalog from within the product itself. For example, let’s imagine the scenario where you are a developer working on your integration flow in Anypoint Code Builder. You want to identify a connector that matches your current needs and utilize it in your integration journey. You can search through your exchange catalog without leaving Anypoint Code Builder, view details regarding the connector, select it, and import it within your flow all from Anypoint Code Builder interface. Support like this makes it even easier to reuse assets and empowers the developer with efficiency – which is the entire goal of Exchange. On the bottom, we have identified a few internal user journeys, all of which are tailored towards managing metrics of assets and producing new asset types. This is important because it is how the catalog core functionality grows. Support of new asset types, for example support of latest versions of AsyncAPIs, is important as it helps us keep up with industry standards and serve a wide range of developer needs.
- Here you can see a list of assets that are currently supported in Exchange. Broken down by APIs, Integration assets, and Automation assets. We support over 25 types of assets. APIs: Anypoint Exchange hosts APIs that developers can explore, consume, and leverage in their own applications. We recently launched a new console for GraphQL, and are working to support the latest version of AsyncAPIs that is inline with industry standards for event driven architecture. The integration assets, specifically connectors, examples, and templates, are critical when it comes to reusability. Let’s briefly define these asset types. Connectors provide the means for developers to easily integrate various systems into their MuleSoft applications. Templates are pre-built flows that address use cases or business processes and serve as starting points for devs to quickly build and customize their own integrations. Examples demonstrate how to implement specific integration scenarios. There are a wide variety of MuleSoft provided assets, primarily including bundles of templates, examples, and connectors tailored to specific business use cases and industries, which can be quickly utilized. You can view these on the Exchange home page, under the ‘Provided by MuleSoft’ tab.
- Given all this, it is apparent that our customers care about reuse. In fact, that is a key differentiating factor between our API catalog and various other market offerings. Not only do our customers value the concept of reusability, as you can see from this slide – they want to understand current data on reuse. This information is important to them because it helps them understand where and how their APIs are being engaged with. This can help them better design valuable and helpful APIs moving forward.
- So, how is reuse actually defined? In some sense, reusability is the potential a component has to be reused, whereas reuse itself is the true repeated usage of that specific component. Other industry definitions include Gartners, which is “an application development methodology that catalogs and makes available various components so that they may be incorporated into other applications”. Or we can also think of reuse as “the ability of an application to be used more than once without change into a new system.” In some sense, reuse is higher when something is designed as solution agnostic. And the true power lies in the ability of the overall application to be customized and extended on top of that reused component.
- The concept of engagement, reusability, and usage tracking is not unique to the enterprise IT space. In fact, we see it all around us in almost every application of tech we interact with on a daily basis. Let’s take the example of online marketplaces. Engagement here is measured by the number of purchases made or perhaps the # of recommendations given. Additionally, you would look at # of producer ‘uploads’ or # of buyer purchases for engagement as well. Another good example is that of social networks. Engagement here might be tracked by the # of shares of a specific post, # of views, or # of likes. In principle, we care about 5 key things when it comes to quantifying engagement and usage. First, it is essential to define ‘active engagement’. Which actions qualify as true engagement with the product, Or in our case with the API. Next we must define the relative importance of the various engagement actions. In our API example, we might want to understand how downloads compare to imports? Monitoring this engagement will help us create a baseline. Next, we can create a custom algorithm to analyze the various actions in context and relativity, and compute an aggregate engagement metric. And finally, we can deliver these insights to the users, thus ultimately closing the feedback loop.
- Driving efficiency through reuse is a pillar of Exchange’s core value proposition – reusable, pre-built assets help jumpstart the developer journey. And as we discussed at the beginning of this presentation, the concept of reusability really drives network effects of the platform, thus making your users more efficient. Here are three key tangible benefits of this concept in practice: The hundreds of connectors and pre-built templates offered by MuleSoft can be used to jumpstart the integration journey at any point of need Exchange acts as the centralized hub for all of this content, and both assets created by your organization along with those provided by mulesoft can be accessed from this centralized point. This, along with the adherence to governance and lifecycle management ensures high quality. These quality assets can also be shared with users within and across business groups, thus reducing overall time to market. And finally, the new feature that we will dive into next will help developers understand usage data which closes the overall feedback loop
- Let’s take a look now at the new Exchange feature which hits on this value proposition.
- This feature is already available and can be accessed from the left navigation menu on the Exchange home page. To emphasize once again, the way this data is calculated is in line with the principles behind engagement mentioned before. The drivers behind the Exchange asset engagement score are the various consumption actions that users make across various points of the platform. The score then reflects the overall engagement and reusability of the asset as a portion of the total assets in the customer root organization. This score also helps developers quickly understand and identify useful assets that they can then reuse to build their application.
- And once again you can also view asset engagement data for specific API Versions, to better understand how a specific asset version contributes to the overall engagement of the asset. This is extremely helpful as you can see which asset versions are key drivers of reuse.
- With that, I have an exciting announcement to make! We are launching engagement metrics for 3 new asset types: Connectors, Examples, and Templates. This will help drive a deeper understanding of integration asset reusability. Support for these asset types is highly requested, as the core purpose of these asset types is providing those integration journey shortcuts.
- A big question you might be thinking of is how can this information be used? In short, the usage and engagement data is extremely valuable in helping you better manage your catalog and drive value to end consumers. The first step in realizing this goal is understanding baseline engagement. That is achieved through the dashboard as shown in the demo. Next, you want to improve the overall quality of the assets. You can do this by adding asset icons and an asset name that is easy to understand and reflects the purpose of the asset. This will also make it easier for users to quickly find the asset. Next, you want to educate users on how to use the asset. This can be done by adding detailed asset documentation. There are several best practices that we recommend here, which can help you achieve this goal. Another part of improving discoverability and usability is adding asset metadata through tags, categories, and custom fields. You can also ensure proper catalog hygiene by updating assets as they move through the software development lifecycle, marking assets and specific versions that are no longer relevant as deprecated, and promoting stable and conformant versions with the right tags. All of these steps are easy to take and can help make your catalog more robust.
- Looking forward this year, we have quite a few exciting releases on the radar! In addition to engagement metrics for connectors, examples, and templates, we are working on launching recommendations for Exchange users based on the data. This will help drive the business value of engagement metrics, by helping you understand what you can do based on the engagement score. In essence, this feature will help you implement the various steps mentioned on the previous slide. Other interesting callouts: we will be adding a feature to make it possible for client application owners to add additional owners (individual users or teams) from the my application page on Exchange. This will make it easier for the management of client applications in the case that the original owner is unreachable. Finally, today we have full feature parity between the two search experiences. Thus, we will work to deprecate the legacy experience.
- And very briefly, let’s take a look at what was recently released. In February, a new feature reflecting Java 17 compatibility for connectors was launched. When a connector is published to exchange, it will extract the Java compatibility metadata and store it as a custom property. Exchange will also run a script to populate this property for all existing connectors (Java 8 / Java 11). Now, when you click on the view versions button of an API in the portal page, you can view both the Mule Runtime version as well as the compatible Java versions for a given connector version.
- In November, we released a new custom field metadata filter to enhance your search and discovery journey. A custom field is a key-value pair that can be added to an asset version, acting as a unique identifier to help you quickly discover your asset. These custom fields can be added to an asset via the Exchange API. Assets can be filtered by custom fields to refine a search using this preset information. The custom field filter is available only when assets in your organization contain custom fields.
- I’d love to stay in touch with the community! Greatly appreciate any feedback you have, and would also love to be in touch for feedback as we iterate through new feature development. Please don’t hesitate to reach out with any questions or just to chat.
- Feel free to reach out with any questions!