CloudHub Interview Question
CloudHub Interview Question
CloudHub Interview Question
Cloud hub
On-premise
Runtime Fabric(RTF)
Anypoint PCE(Anypoint Private Cloud Edition)
Anypoint PCF(Anypoint Platform for Pivotal Cloud Foundry)
What is Cloudhub?
Cloudhub is an (iPasS) Integrated platform as a service which is multi-tenant, secure, highly
available service where we can deploy our integration application on cloud also integrate on-
premise application with cloud services
How many ways you can deploy application on Cloudhub?
Anypoint Studio
Runtime Manager
Anypoint CLI
Cloudhub API
With Anypoint Platform Private Cloud Edition (Anypoint Platform PCE), you run and
manage Mule applications on your local servers
Anypoint Platform PCE uses Docker and Kubernetes to provide built-in high availability
and scalability.
You can install the platform without understanding Docker or Kubernetes
With Cloud hub deployment strategy you can deploy maximum 10 Application on 1 vCore
machine but in on-premise you can deploy 100 application on 1 vCore depends on the
In Cloudhub mule runtime will be managed by the MuleSoft, in on-premise mule runtime
will be managed by the Customer itself
How can one mule app access the object store of another mule app?
To share data between Mule 4 apps create a flow to retrieve the data using the Retrieve
operation in the Object Store Connector
What is Anypoint MQ?
What is API Manager?
API Autodiscovery is used to pair the API in API Manger to it deployed mule application
When autodiscovery is correctly configured in your Mule application you can say that
your application’s API is tracked by or paired to API Manager.
An API in a Mule runtime can only be associated with one autodiscovery instance. No
two Autodiscoveries can be associated to the same API in a Mule Runtime.
XML or JSON threat protection – this will protect against the oversized XML or JSON
payload
Client ID enforcement – authentication is need for proper use of an API, only client
authorized can use the API and no one else
SLA-based Rate Limiting – this is more need in case we want to monetize an API
otherwise ignored e.g.
Free – 20 request per minute
Unlimited – 100K request per minute
IP blacklisting – this can be used if we want to limit the consumption of an API to
particular IPs e.g. IPs know for hacking etc.
Tokenization – to tokenize any element which can be sensitive e.g. credit cards etc.
HTTP Caching – in case we think the response don’t change frequently and it’s ok to
send the same response for particular request
Design center can be used to write API definitions with RAML using API Designer
You can also create API Fragment in RAML, after you create a specification or fragment
you can publish it to Anypoint Exchange so that it can be reused in the organization
Design center can also be used to create mule applications using flow designer
%dw 2.0
Import java!com.mycompany::classname
output application/json
---
{
a: classname::methodName("myString")
}
Do not save the Payload in to the flow Variable as it is more memory consuming
element
Do not load unnecessary part of the document
Use better Database polling for highly concurrent scenarios
If we wanted to process only one message at a time in mule flow how can we
achieve that?
we can make a flow to process in single thread, there is an option to define the Max
Concurrency you can configure the same as 1 to process only one message at a time
What is runtime manager?
Runtime manager is to deploy and manage mule application on mule runtime engine,
where mule runtime is running on Cloudhub or on-premise or on RTF.
By using runtime manage you can deploy/undeploy the mule app
You can change the runtime version at any time
You can increase/decrease the worker size
What is vCore?
It is unit of compute capacity for processing on Cloudhub. In 1 vCore maximum 10 applications
can be deployed where 0.1 vCore will be consumed by each mule application
What is worker in MuleSoft?
Worker is an dedicated Instance of Mule hosted on AWS is used to run your integration
application
Features of workers:
Capacity: Each worker has a specific amount of capacity to process data.
Isolation: Each worker run in a separate container from every other application
Manageability: Each worker is deployed and Managed independently
Locality: Each worker runs in specific worker cloud such as US,EU or Asia-Pacific
How many mule applications you can deployed in one worker in Cloudhub
Only one Mule Application can be deployed in MuleSoft in one worker
What is minimum and maximum Worker size available in Cloudhub?
0.1 vCores is the Minimum and 16 vCores is the maximum worker size available in Cloudhub
What is horizontal scaling and vertical scaling?
Vertical scaling is to increase the worker size, when you want to process the CPU Intensive
API’s or process large payload with small number of request increase the vCore size.
Horizontal scaling is to increase the number of worker, if you want to increase the throughput of
high frequency small payload
How to achieve clustering in MuleSoft
You can achieve this by adding multiple workers to your application to make it horizontally scale,
Cloudhub automatically distribute multiple workers for same application across 2 or more data
centres for maximum reliability When deploying your application to two or more workers, the
HTTP load balancing service distributes requests across these workers, allowing you to scale
your services horizontally. Requests are distributed on a round-robin basis.
Can you disable the Cloudhub Logs?
Yes, in that case only the system logs are available in Runtime Manager. System logs provide
the status of your worker deployment and whether your application started correctly, but do not
provide application logs
What is Mule Runtime?
A Mule runtime is a runtime engine used to host and run Mule applications – Similar to an
application server
Mule runtimes can be provisioned on-premises and/or in the cloud
One Mule runtime can host several Mule applications
What all different API policies should be applied on different API levels like Experience,
Process and System Level?
Experience
Client ID enforcement – authentication is need for proper use of an API, only client
authorized can use the API and no one else
SLA-based Rate Limiting – this is more need in case we want to monetize an API
otherwise ignored e.g.
Free – 20 request per minute
Unlimited – 100K request per minute
IP blacklisting – this can be used if we want to limit the consumption of an API to
particular IPs e.g. IPs know for hacking etc.
Tokenization – to tokenize any element which can be sensitive e.g. credit cards etc.
HTTP Caching – in case we think the response don’t change frequently and it’s ok to
send the same response for particular request
Cross-Origin resource sharing – is a standard mechanism that allows JavaScript
XMLHttpRequest (XHR) calls executed in a web page to interact with resources from
non-origin domains. CORS is a commonly implemented solution to the “same-origin
policy” that is enforced by all browsers.
Process
IP whitelisting – making sure the request are coming from allowed VPC or within
organization
SLA-based Rate Limiting – it will make sure that target system will not go down in case of
burst request
Client ID enforcement – authentication is need for proper use of an API, only client
authorized can use the API and no one else
System
IP whitelisting – making sure the request are coming from allowed VPC or within
organization
SLA-based Rate Limiting – it will make sure that target system will not go down in case of
burst request
Client ID enforcement – authentication is need for proper use of an API, only client
authorized can use the API and no one else
Multi-factor Authentication
Token-based authentication
Digital signature
Public key cryptography
Digital certificate