Mule Application Development: Effective Caching
ICYMI: In any integration project, caching is a crucial part of the design. Certain data are very unlikely to change for a period of time. In those situations, we do not want to retrieve the data everytime from a data source, such as a database, file, etc.
Mule Anypoint Platform provides two key caching mechanisms. One is context registry, which basically is a Java HashMap inside the MuleContext object. We can use the registry to store and retrieve data. The other is cache scape, which stays inside a flow or sub-flow. When the system hits the component, it checks its cache. If it has the key, it will return the value. Otherwise, it will invoke the cache scope, which typically will retrieve data from data sources. For more details about the cache component, please refer to Mule documentation here. https://goo.gl/g3bja3 #DataIntegration #ML
SAP Integration in Mule ESB
Currently, SAP is at the core of most enterprises and needs to connect various systems. Mule ESB provides a connector that enables integration of data with SAP NetWeaver and external systems.
Requirements: https://goo.gl/8V4F4u #DataIntegration #ML
Connecting a PostgreSQL Database With Apache Camel
The jdbc: component allows you to access a database using JDBC, whereas the Select query and operations (UPDATE, INSERT, DELETE etc.) send messages in bodies.
The sql: component allows you to work with databases using JDBC queries. The difference between this component and the JDBC component is that, with SQL, the query is a property of the endpoint, and it uses message payloads as parameters passed to the query. https://goo.gl/S5QZhk #DataIntegration #ML