<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Prashanth Kurimella on Medium]]></title>
        <description><![CDATA[Stories by Prashanth Kurimella on Medium]]></description>
        <link>https://medium.com/@pkurimella?source=rss-3cb57434152a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*zSlXcYoIgTjgip0bOSyEDg.jpeg</url>
            <title>Stories by Prashanth Kurimella on Medium</title>
            <link>https://medium.com/@pkurimella?source=rss-3cb57434152a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 01:45:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pkurimella/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Keeping up with MuleSoft Runtime Patches]]></title>
            <link>https://medium.com/another-integration-blog/keeping-up-with-mulesoft-runtime-patches-fd700730db43?source=rss-3cb57434152a------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd700730db43</guid>
            <category><![CDATA[integration-platform]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[mulesoft]]></category>
            <category><![CDATA[anypoint-platform]]></category>
            <category><![CDATA[security-update]]></category>
            <dc:creator><![CDATA[Prashanth Kurimella]]></dc:creator>
            <pubDate>Mon, 27 Mar 2023 17:21:01 GMT</pubDate>
            <atom:updated>2023-03-27T17:21:01.419Z</atom:updated>
            <content:encoded><![CDATA[<p>Several high-profile data breaches have occurred due to vulnerabilities that could have been mitigated or prevented by simply updating or patching the affected software or systems.</p><p>This article provides an overview of how MuleSoft provides patches to its runtimes, how these patches could be applied to various MuleSoft &amp; Customer hosted runtimes as well as a strategy to validate and test these patches.</p><figure><img alt="Searching code for vulnerabilities" src="https://cdn-images-1.medium.com/max/1024/1*HaVF_8gkz0OxfPsnrHX57g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/ja/@gamell?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Joan Gamell</a> on <a href="https://unsplash.com/photos/XmZ4GDAp9G0?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>MuleSoft provides Runtime <a href="https://docs.mulesoft.com/release-notes/mule-runtime/upgrade-update-mule">updates</a> that typically include bug fixes, security patches, and new features. Keeping up with these updates protects your business and customers from various threat factors and attacks that might compromise critical data.</p><p><strong>MuleSoft </strong>follows semantic versioning for releases. <strong>Major releases </strong>are significant updates that introduce new features and functionality, while <strong>Patch releases</strong> are smaller updates that address bugs and security vulnerabilities.</p><p>Major and Minor version releases are bundled with new features and functionality. Tech teams often need time to leverage the newer runtimes by making the updates as part of a release or a delivery schedule. Patch releases are cumulative releases that are published frequently and are well-tested for backward compatibility. As newer threats and issues are identified globally every month, it is a good practice to establish a recurring patching schedule to minimize risks and reduce interruptions for businesses.</p><h4>Why are patches to MuleSoft Runtimes critical?</h4><p>MuleSoft runtime updates are critical for businesses using the platform. These updates provide several benefits, including:</p><ol><li><strong>Improved Security</strong>: MuleSoft regularly releases security patches to address known vulnerabilities in the platform. These updates help protect businesses’ sensitive data and prevent unauthorized access to their systems.</li><li><strong>Bug Fixes</strong>: Runtime updates also include bug fixes, which improve the stability and reliability of the platform. These fixes can help prevent system crashes and improve the overall performance of integration workflows.</li><li><strong>New Features</strong>: Major releases of the Mule runtime often introduce new features and functionality that can help businesses streamline their operations and improve efficiency. These updates can include new connectors, integration patterns, and tools for monitoring and managing integrations.</li><li><strong>Compatibility</strong>: Runtime updates ensure that MuleSoft remains compatible with the latest operating systems, databases, and other software components. This compatibility ensures that businesses can continue to integrate new systems and applications as they become available.</li></ol><h4>How do you install MuleSoft Runtime Patches?</h4><p>Installing patches varies by the deployment strategy chosen by organizations.</p><p><strong>CloudHub</strong>: CloudHub 1.0 and 2.0 Runtimes are hosted and managed by MuleSoft. Hence updates are automatically applied at least once a month to ensure your applications are running with all critical security patches and backward-compatible bug fixes.</p><blockquote>Applications running in sandbox environments are updated during weekdays while applications in production are updated during weekends. If your application required manual updates due to critical processes or cannot support rolling updates then you can plan for applying runtime updates before the automatic updates are triggered. Refer to <a href="https://docs.mulesoft.com/cloudhub-1/cloudhub-app-runtime-version-updates#update-schedule">CloudHub 1.0</a> and <a href="https://docs.mulesoft.com/cloudhub-2/ch2-patch-updates">CloudHub 2.0</a> update schedules.</blockquote><p><strong>Standalone Runtimes (Customer Hosted): </strong>Businesses can either use the Mule Upgrade tool to update their runtime or manually download and install the latest runtime version. The Mule upgrade tool also updates the mule agent as well as handles upgrades to clustered runtimes by upgrading one node at a time to minimize downtime.</p><blockquote>The <a href="https://docs.mulesoft.com/mule-runtime/4.4/mule-upgrade-tool">Mule Upgrade tool </a>is a command line utility for upgrading Mule Runtimes and Mule Agent. The tool can be packaged along with other scripts to automate the process of upgrading and patching the runtimes.</blockquote><p>Updates to operating systems, firewalls, and network components are the customer’s responsibility.</p><p><strong>Runtime Fabric (Self Managed: AKS, EKS, GKE, or RedHat OpenShift): </strong>Runtime Fabric(RTF) consists of multiple components running on a Kubernetes cluster managed on-premise or in the cloud. Updates are required for all Core Runtime Fabric components as well as Mule Runtimes used by applications.</p><p>Runtime Fabric now supports hosting all images in the enterprise or usingMuleSoft hosted private ECR. For customers hosting images in the local registry, images with Mule Runtime updates and patches have to be pulled from MuleSoft’s private ECR using secure credentials provided via Anypoint Platform.</p><blockquote>Similar to CloudHub, MuleSoft enforces customers on Runtime Fabric to keep up with Mule Runtime updates. As MuleSoft releases monthly patches, the control plane enforces new deployments or updates to existing ones using new <a href="https://docs.mulesoft.com/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes">MuleSoft Runtime Images</a> only.</blockquote><p>In addition to Mule Runtime updates, RTF consists of several core services running in an isolated namespace (rtf) that require updates. RTF managed on AKS, EKS, and GKE can be <a href="https://docs.mulesoft.com/runtime-fabric/2.1/upgrade-index">upgraded</a> via <em>rtfctl</em> a command line utility, or via <em>helm</em>. OpenShift updates can be run automatically or manually via the OpenShift <em>console</em>.</p><p>All Kubernetes and Host system updates are the customer’s responsibility per the <a href="https://docs.mulesoft.com/runtime-fabric/2.1/#anypoint-runtime-fabric-as-a-shared-responsibility">Shared Responsibility</a> model. It is a good practice to refer RTF version compatibility before upgrading your Kubernetes cluster.</p><h4><strong>How to validate MuleSoft updates and patches?</strong></h4><p>Keeping up with updates is a good practice but often requires a strategy or a plan in place to support the rollout of updates while ensuring that it doesn’t application behavior.</p><blockquote>MUnits can be configured to run on a specified runtime release or a patch version to help validate and test Mule applications before applying specific releases to MuleSoft runtimes.</blockquote><p><a href="https://docs.mulesoft.com/munit/2.1">MUnits</a> are a great way to automate the testing of Mule applications. Having a proper set of test cases and good coverage would often help accelerate testing. MUnits can be configured to run on a specific <a href="https://docs.mulesoft.com/munit/2.1/runtime-patching">MuleSoft patch version</a>. MUnit patching and testing can be run independently from Mule Runtime patching allowing us to validate patches ahead of planned upgrade schedules.</p><h3>Conclusion</h3><p>MuleSoft Runtime updates and patches are critical for ensuring the reliability, security, and performance of the platform. By staying up to date with the latest runtime version, businesses can take advantage of new features and functionality while protecting their data from security vulnerabilities. Refer to MuleSoft Runtime patches <a href="https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions">here</a> for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd700730db43" width="1" height="1" alt=""><hr><p><a href="https://medium.com/another-integration-blog/keeping-up-with-mulesoft-runtime-patches-fd700730db43">Keeping up with MuleSoft Runtime Patches</a> was originally published in <a href="https://medium.com/another-integration-blog">Another Integration Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MuleSoft Policies: Govern and Manage APIs efficiently]]></title>
            <link>https://medium.com/@pkurimella/mulesoft-policies-govern-and-manage-apis-efficiently-5dee0d7656db?source=rss-3cb57434152a------2</link>
            <guid isPermaLink="false">https://medium.com/p/5dee0d7656db</guid>
            <category><![CDATA[mulesoft]]></category>
            <category><![CDATA[anypoint-platform]]></category>
            <category><![CDATA[api-management]]></category>
            <category><![CDATA[api-gateway]]></category>
            <category><![CDATA[mulesoft-policies]]></category>
            <dc:creator><![CDATA[Prashanth Kurimella]]></dc:creator>
            <pubDate>Mon, 13 Apr 2020 19:17:26 GMT</pubDate>
            <atom:updated>2020-04-13T19:17:26.500Z</atom:updated>
            <content:encoded><![CDATA[<p>API Manager provides ability to efficiently govern and manage APIs. One of the key elements of API Manager is Policies and this article focuses on the use cases from an API Layer point of view.</p><figure><img alt="API Manager’s Governance using API Gateway in Mule Runtime Engine" src="https://cdn-images-1.medium.com/max/1024/0*fIM9kxQHw-2QUgCI.png" /><figcaption>Role of API Manager in MuleSoft</figcaption></figure><h4><strong>What are policies?</strong></h4><blockquote>Policies enable you to enforce regulations to help manage security, control traffic, and improve adaptability of your APIs. For example, a policy can control authentication, access, allotted consumption, and service level access (SLA).</blockquote><p>Enforce these regulations to APIs without any code changes. Policies could be applied across any APIs implemented on Anypoint Platform as well as using proxies for APIs implemented out of Anypoint Platform.</p><p>API Manager provides default policies providing handling different aspects of security, management and governance. In addition to the default policies, <a href="https://docs.mulesoft.com/api-manager/2.x/custom-policy-getting-started">custom policies</a> could also be created and applied to suit any custom needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*KD0rucwNbY54XApkqW687A.png" /><figcaption>Apply Policy using API Manager</figcaption></figure><h4>Policy Categories</h4><p>Default Policies available within API Manager are mainly categorized based on functionality they provide. <a href="https://docs.mulesoft.com/api-manager/2.x/policies-policy-categories">Categories </a>available are</p><ul><li><strong>Security </strong>: Policies available in this category are for enforcing Authentication (Choose between methods such as Basic, OAuth2.0, JWT etc), allow / deny access based on IP Range (IP Black / White listing).</li><li><strong>Compliance </strong>: Enforce requirements such as Client ID and CORS.</li><li><strong>Transformation </strong>: Allows to transform / enrich headers for request or response. This could be used to add or remove any default or sensitive information from within the headers.</li><li><strong>Quality of Service</strong> : QoS based policies mainly provide SLA support, Spike control to queue traffic and Caching.</li><li><strong>Troubleshooting </strong>: For troubleshooting incoming requests by logging messages.</li></ul><h3>Applying Policies across API Layers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/0*owjRB9eT-dr7o_0k.png" /><figcaption>API Layers — API-led Connectivity</figcaption></figure><p>While any of the default policies available could be used on any API some factors such as Authentication, Protection, Access, Performance, Usage etc could help us pick the right set of policies required across each API.</p><h4><strong>Experience APIs</strong></h4><p>Since these APIs are more front line and often exposed out, policies that enforce protection from threats, API security and usage are essential.</p><p><em>Policies Applicable: OAuth, JWT, JSON / XML Threat Protection, Rate Limiting, SLA Based, Caching</em></p><p><strong>Authentication </strong>: Use one of OAuth 2.0 or JWT policies to protect from anonymous usage. If only LDAP is available then use Basic Authentication — LDAP. Additional Auth</p><p><strong>Protection </strong>: Use JSON / XML threat protection policies to protect against dangerous payloads. Additionally IP Blacklist policy could be used to block traffic from frequent violators or well known dark nets.</p><p><strong>Access </strong>: When API is consumed by a Web Application, use CORS to enable access for enable or disable access from other domains.</p><p><strong>Usage Monitoring &amp; Limits</strong> : Use Rate limiting / SLA-Based policy to enforce limitations on API usage.</p><p><strong>Performance </strong>: Use HTTP caching to cache responses and optimize resource usage by serving cached data. Caching could be limited based on time, method or further customized based on need when applying.</p><p><strong>Customize Headers</strong>: Use Header Injection to add custom meta data for processing requests down stream or for responses such as to security signatures etc. Similarly use Header removal to remove any sensitive data being sent through headers such as HSTS info.</p><h4>Process APIs</h4><p>These APIs are central and essentially handling core business rules and coordinating requests to one or more downstream system APIs. Policies that help with performance yet enforce some security without having impact on performance is a common requirement.</p><p><em>Policies Applicable: Basic Authentication, Spike Control, IP White Listing, Rate Limiting, Caching, Header Injection &amp; Removal.</em></p><p><strong>Authentication </strong>: Since Process APIs are usually internal and mostly consumed by Experience APIs, Basic Authentication would be ideal.</p><p><strong>Protection </strong>: In some cases spike control could help to limit amount of requests being sent to downstream APIs if downstream APIs are under performing due an outage / when using DR Services.</p><p><strong>Access </strong>: IP White listing could be used to limit access to a dedicated set of consumers. This policy accepts IP(s) and also IP Range(s). Use this policy to white list IP’s of upstream APIs (Experience APIs).</p><p><strong>Usage Monitoring &amp; Limits</strong> : Use Rate Limiting policies to track and limit usage.</p><p><strong>Performance </strong>: Use HTTP caching to cache responses and optimize resource usage by serving cached data. Caching could be limited based on time, method or further customized based on need when applying.</p><p><strong>Customize Headers</strong>: Remove headers returned from downstream APIs using Header Removal Policy or Inject headers such as Client IDs using Header Injection Policy.</p><h4>System APIs</h4><p>These APIs are highly used and often communicating with data sources or third party systems. Reliability and performance would be key elements to factor in.</p><p><em>Policies Applicable: Basic Authentication, Spike Control, IP White Listing, Rate Limiting, Caching, Header Injection &amp; Removal.</em></p><p><strong>Authentication </strong>: Similar to Process APIs, System APIs are internal and mostly consumed by Process APIs, Basic Authentication would be ideal policy for Authentication.</p><p><strong>Protection </strong>: Use spike control if System APIs provide access to legacy systems that cannot multitask or accept huge amount of requests.</p><p><strong>Access </strong>: IP White listing could be used to limit access to a dedicated set of consumers. This policy accepts IP(s) and also IP Range(s). White list upstream API IP Addresses(process APIs).</p><p><strong>Usage Monitoring &amp; Limits</strong> : Use Rate Limiting policies to limit usage of API or a specific operation(s). For ex: a third party app only allows certain amount of operations per day. Use this to limit # of transactions being submitted.</p><p><strong>Performance </strong>: Use HTTP caching to cache responses and optimize resource usage by serving cached data. Caching could be limited based on time, method or further customized based on need when applying.</p><p><strong>Customize Headers</strong>: Remove headers returned from downstream APIs / Systems using Header Removal Policy.</p><h3>Mule 3 vs 4</h3><p>While most of the policies mentioned above are applicable to both Mule 3 and 4, some differences could exist in terms of configuration or support.</p><p><a href="https://docs.mulesoft.com/api-manager/2.x/policies-compare-mule3-and-mule4">Comparison of Policies Features Based on Mule Versions</a></p><h3>Conclusion</h3><ol><li>Number of Policies : Efficiently apply policies. Increased number of policies could effect APIs performance as they are executed in the runtime.</li><li>Order of Policies : Policies are executed in the same order as they are listed in API Manager when sending request to API as well as executed in the reverse order when sending response. Applying policies like threat protection , caching earlier could help with performance.</li><li>Automated Policies : Use <a href="https://docs.mulesoft.com/api-manager/2.x/automated-policies-landing-page">automated policies</a> to enforce global policies based on Runtime or additional criteria.</li><li>Custom Policies : Use <a href="https://docs.mulesoft.com/api-manager/2.x/policies-custom-landing-page">custom policies</a> to apply business needs that are not met using default policies.</li></ol><p><strong>References</strong></p><ul><li><a href="https://docs.mulesoft.com/api-manager/2.x/latest-overview-concept">Reviewing API Manager concepts</a></li><li><a href="https://docs.mulesoft.com/api-manager/2.x/policies-landing-page">Policies</a></li><li><a href="https://docs.mulesoft.com/api-manager/2.x/automated-policy-apply">Applying Automated Policies</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5dee0d7656db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MuleSoft Deployment Strategies & their Differences (RTF vs Hybrid vs CloudHub)]]></title>
            <link>https://medium.com/@pkurimella/mulesoft-deployment-strategies-rtf-vs-hybrid-vs-cloudhub-e5aa241c365f?source=rss-3cb57434152a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5aa241c365f</guid>
            <category><![CDATA[mulesoft]]></category>
            <category><![CDATA[integration]]></category>
            <category><![CDATA[runtime-fabric]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[cloudhub]]></category>
            <dc:creator><![CDATA[Prashanth Kurimella]]></dc:creator>
            <pubDate>Thu, 02 Apr 2020 13:56:16 GMT</pubDate>
            <atom:updated>2020-04-02T14:31:02.252Z</atom:updated>
            <content:encoded><![CDATA[<h3>MuleSoft Deployment Strategies (RTF vs Hybrid vs CloudHub)</h3><p>CloudHub, Hybrid and RTF are available as deployment options when using Anypoint’s Runtime Manager. Let’s look at difference between these deployment options and use cases suited for each deployment model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/1*68GVnZJD_ttFUaoHJZDE5w.png" /><figcaption>MuleSoft Deployment Options</figcaption></figure><p>Mule applications are primarily deployed and managed using <a href="https://docs.mulesoft.com/runtime-manager/">Runtime Manager</a>. Runtime Manager is available both on Cloud based Anypoint Platform and Private Cloud Edition. Runtime Manager primarily supports 4 deployment options and each option is available based on which Runtime Manager is being used.</p><h3>Deployment Options</h3><h3>CloudHub</h3><p>Fully-managed &amp; highly available service provided by MuleSoft to run mule applications in the cloud without having to provision / manage any servers or cloud resources. CloudHub is available globally in <a href="https://docs.mulesoft.com/runtime-manager/cloudhub-architecture#global-worker-clouds">multiple regions</a>. CloudHub also provides secure and out of the box <a href="https://compliance.salesforce.com/en/services/mulesoft">compliance</a> environment in the cloud.</p><p>CloudHub also comes with Auto / Manual <a href="https://docs.mulesoft.com/runtime-manager/managing-applications-on-cloudhub#scaling-your-application">scaling </a>without redeployment, inbuilt integration with Anypoint Studio IDE to quickly deploy apps, API to <a href="https://docs.mulesoft.com/runtime-manager/managing-applications-on-cloudhub">manage </a>and monitor applications.</p><p>Best suited for Experience APIs, Process APIs or Cloud to Cloud Integrations and Securely exposing APIs for Enterprise Systems hosted on premise.</p><h3>Hybrid (Mule Servers On Premise)</h3><p>Run mule applications on your own Mule Servers by deploying and managing through Runtime Manager. Mule Applications could be run on servers hosted on premise / data center or in Cloud. Each Server has to be registered with Runtime Manager and then organized into Server Group or Clusters for high availability. Deployment and Management of Mule Apps onto Hybrid Servers are performed through Runtime Manager. Additionally Runtime Manager also provides <a href="https://docs.mulesoft.com/runtime-manager/monitoring">Monitoring </a>of all deployed applications.</p><p>Best suited for System APIs integrating with enterprise systems hosted on premise, Process APIs that communicate with Multiple Systems APIs for reduced latency and / or compliance, Experience APIs for Inter-Network Apps and Batch Processing Apps processing large volumes of data on premise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/258/0*i1SN4cxAZzJ2_w5G" /></figure><p>Note: Although Clustering Mule Runtime engines provide high availability it is still dependent on nodes availability and # of instances of mule apps running are dependent on # of clusters / servers. Auto-recovery of node is not available. Each runtime is limited to a specific version and any upgrades would require downtime.</p><h3>Anypoint Runtime Fabric</h3><p>Runtime Fabric (RTF) is a container based service that provides iPaaS based environment for all customer managed infrastructure whether it be Bare metal Servers / VMs or AWS or Azure. RTF comes with all components required for running Mule Services on a container based environment such as Docker and Kubernetes.</p><p>RTF offers abilities such as running multiple versions of Mule Runtimes on same servers, ability to isolate applications by running one Mule Runtime per application, Auto fail-over and CPU burst make RTF a very promising deployment model. RTF makes it easier to switch between mule versions thus giving an ability to do a phase based 3.x to 4.x migration on the same set of resources without changing the plumbing in place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pjXiY6CVQ-tzOSFk" /></figure><p>Best Suited for Systems APIs, Process APIs, Experience APIs for Inter-Network Apps and ideal all scenarios due to its Cloud like abilities.</p><h3>Anypoint Platform Private Cloud Edition</h3><p>Private Cloud Edition (PCE) bundles the management modules known as control plane into the environment so all components to run and manage apps are on customer managed infrastructure.</p><p>While PCE bundles both Control and Runtime planes, it requires lot of infrastructure and is only effective to be opted out of forced regulatory requirements. Features of PCE might vary from other deployment models as release cycles are often behind. Setting up PCE is also complex when compared to RTF.</p><h3>CloudHub vs Hybrid vs RTF Differences</h3><p>When choosing a deployment model for on premise / data center installation, even through Hybrid might require less hardware RTF provides cloud like ability and flexibility in terms of how applications and resources could be managed effectively.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2F8U7FkJLWEjeOA&amp;display_name=SlideShare&amp;url=https%3A%2F%2Fwww.slideshare.net%2FPrashanthKurimella%2Fmulesoft-deployment-strategies-rtf-vs-hybrid-vs-cloudhub&amp;image=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fmulesoftdeploymentstrategies-200331134646-thumbnail-4.jpg%3Fcb%3D1585662600&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/ffec1a54fc1fb7f3db921617cad8426f/href">https://medium.com/media/ffec1a54fc1fb7f3db921617cad8426f/href</a></iframe><p>The differences listed above are more on hosting and management. Each of these deployment models could have some variations in terms of functional features.</p><p>References</p><ul><li><a href="https://docs.mulesoft.com/runtime-manager/deployment-strategies#cloudhub-deployments">Deployment Options</a></li><li><a href="https://docs.mulesoft.com/runtime-manager/managing-servers">Servers, Server Groups, and Clusters</a></li><li><a href="https://docs.mulesoft.com/runtime-manager/monitoring">Monitoring Applications and Servers</a></li><li><a href="https://docs.mulesoft.com/runtime-manager/custom-application-alerts">Custom Application Alerts and Notifications</a></li><li><a href="https://docs.mulesoft.com/runtime-manager/autoscaling-in-cloudhub">Autoscaling in CloudHub</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5aa241c365f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>