CloudHub object store should be in same region where the Mule application is deployed. This will

give optimal performance.

Before learning about Cache scope and object store in Mule 4 we understand what is in general

Caching is and other related things.

WHAT DOES “CACHING” MEAN?

Caching is the process of storing frequently used data in memory, file system or database which

saves processing time and load if it would have to be accessed from original source location every

time.

In computing, a cache is a high-speed data storage layer which stores a subset of data, so that future

requests for that data are served up faster than is possible by accessing the data’s primary storage

location. Caching allows you to efficiently reuse previously retrieved or computed data.

How does Caching work?

The data in a cache is generally stored in fast access hardware such as RAM (Random-access

memory) and may also be used in correlation with a software component. A cache’s primary purpose

is to increase data retrieval performance by reducing the need to access the underlying slower

storage layer.

Caching in MULE 4

In Mule 4 caching can be achieved in mule using cache scope and/or object-store. Cache scope

internally uses Object Store to store the data.

What is Object Store

Object Store lets applications store data and states across batch processes, Mule components, and

applications, from within an application. If used on cloud hub, the object store is shared between

applications deployed on Cluster.

Cache Scope is used in below-mentioned cases:

● Need to store the whole response from the outbound processor

● Data returned from the outbound processor does not change very frequently

● As Cache scope internally handle the cache hit and cache miss scenarios it is more readable

Object Store is used in below-mentioned cases:

● Need to store custom/intermediary data

● To store watermarks

● Sharing the data/stage across applications, schedulers, batch.

If CloudHub object store is in same region where the Mule application is deployed it will aid in fast

access of data and give optimal performance.

:

Reference: https://blogs.mulesoft.com/dev-guides/how-to-tutorials/anypoint-runtime-fabric/

:

* Sharing Mule applications as templates is a great way to share your work with other people who

are in your organization in Anypoint Platform. When they need to build a similar application they can

create the mule application using the template project from Anypoint studio.

* Anypoint Templates are designed to make it easier and faster to go from a blank canvas to a

production application. They’re bit for bit Mule applications requiring only Anypoint Studio to build

and design, and are deployable both on-premises and in the cloud.

* Anypoint Templates are based on five common data Integration patterns and can be customized

and extended to fit your integration needs. So even if your use case involves different endpoints or

connectors than those included in the template, they still offer a great starting point.

Some of the best practices while creating the template project: - Define the common error handler as

part of template project, either using pom dependency or mule config file - Define common

logger/audit framework as part of the template project - Define the env specific properties and

secure properties file as per the requirement - Define global.xml for global configuration - Define the

config file for connector configuration like Http,Salesforce,File,FTP etc - Create separate folders to

create DWL,Properties,SSL certificates etc - Add the dependency and configure the pom.xml as per

the business need - Configure the mule-artifact.json as per the business need

:

As the Anypoint Platform organization administrator, you can configure identity management in

Anypoint Platform to set up users for single sign-on (SSO).

Configure identity management using one of the following single sign-on standards:

1) OpenID Connect: End user identity verification by an authorization server including SSO

2) SAML 2.0: Web-based authorization including cross-domain SSO

Mule 4 is built to:

•

Minimize the need for custom code.

•

Avoid the need for you to know or understand Java.

However, some advanced uses cases require integration with custom Java code, such as:

•

Reuse of a library, such as a tax calculation library.

•

Reuse of a canonical object model that is standard in the organization.

•

Execution of custom logic using Java.

Mule ref doc : https://docs.mulesoft.com/java-module/1.2/

:

* As per definition of API by Mulesoft , it is Application Programming Interface using HTTP-based

protocols. Non-HTTP-based programmatic interfaces are not APIs.

* HTTP-based programmatic interfaces are APIs even if they don’t use REST or JSON. Hence

implementation based on Java RMI, CORBA/IIOP, raw TCP/IP interfaces are not API's as they are not

using HTTP.

* One more thing to note is FTP was not built to be secure. It is generally considered to be an

insecure protocol because it relies on clear-text usernames and passwords for authentication and

does not use encryption.

* Data sent via FTP is vulnerable to sniffing, spoofing, and brute force attacks, among other basic

attack methods.

Considering the above points only correct option is

-XML over ActiveMQ

- XML over SFTP

- XML/REST over HTTPS