Learn with Mule

A brief Context Integration Platform, at its core is a transformation engine that should support robust data mapping features and enables streamline communication between different components of connecting systems and processes. Mulesoft, platform traditionally supported mapping tasks with the component architecture and designed a DataMapper as their first pass to data transformation activities. As the platform matured, Mulesoft coupled the transformation engine with Mule runtime to design a elegant and lightweight expression language based on JSON syntax, Dataweave. Dataweave Environment Design time capabilities of Dataweave lets you define the message metadata which is automatically detected with Datasense. It also accepts several mime-types set at design time on different message processors and defaults to application /java. Explicitly setting the mime type in variable and payload processor parses the java string into standard content. A simple data mapping file has...

Context In Design with Mule - 101, we understood that mule runtime addressed integration challenges by creating components, filters and flow as a medium passing payload from Station A to Station B. Application Developers, primarily adept at Spring frameworks, used mule ESB & even extended to create custom enterprise service bus implementations. I, being an Integration Developer & not core Java Developer had relied on Java EE 6 implementations & SOA enablement tools from Oracle Weblogic ecosystem, and there are others like me from IBM Webspehere ecosystem. It is quite important to differentiate Application Integration from System Integration, but either ways, it would be really beneficial to learn underlying principles of Spring framework like Dependency Injection, cross cutting concerns and how packaging of spring modules are defining next generation Microservices architectures. Mulesoft Anypoint Platform offering has approached on-premise & cloud deployments...