The batch scope within a MuleSoft application enables the ability to process a message as a batch, splitting the incoming payload into individual records to be processed. While the default values within this scope can be used, considerations around what these default values provide along with implications of these chosen values are explained within this article.
The batch scope configurations to be discussed are limited to just the General configurations. For reference, the default values for this configuration are shown below:
MuleSoft’s Dallas API Workshop was an educational and enlightening day dedicated to exploring the value and potential of APIs and harnessing the power of API-led development. Throughout the intervening week, we’ve found ourselves returning again and again to the day’s theme to extract and absorb every last insight. One can hardly overstate what APIs represent for the future of business agility or their centrality to digital transformation.
MuleSoft’s 2017 CONNECT is shaping up to be a great one. So many opportunities to gain insights from MuleSoft experts, hands-on learning and networking opportunities, as well as learning about new MuleSoft capabilities. See my blog for further details regarding top sessions and workshops at CONNECT.
With MuleSoft Connect right around the corner, now is a good time to develop your strategy for sessions and workshops to attend. The workshops, as noted below, require pre-registration, so be sure to sign up sooner rather than later so you won’t miss out.
To help you develop your strategy, AVIO has created a list of top 3 sessions and workshops to attend. Our focus for these picks is on learning about the new tools and features, along with expanding your MuleSoft knowledge.
A tenet of any integration toolset is the ability to interact with databases. With standards in place, this for the most part is fairly easy. But sometimes, the particulars of a database can create some unexpected complexity. One example of this is an integration solution developed within Mulesoft that invokes Oracle PL/SQL stored procedures and functions. In this scenario, knowing about some of the complexity beforehand will ensure less frustration by a developer during the development phase.
The ever increasing number of web and mobile applications continue to drive a lot of discussion around XML vs. JSON when exchanging data. For many systems within an enterprise, this conversation has no relevance, since the exchange of data to/from these systems is limited to only flat file formats. Many of these legacy systems require formats such as comma separated values (csv), fixed length, or hierarchical structures. Mule’s DataWeave has had support for csv transformations.
A digital transformation initiative can revolutionize the way your organization works, allowing employees to boost their productivity. Moving your organization into the digital realm also allows you to keep up with the latest trends in your industry, helping you to remain relevant in a rapidly changing world. However, digital transformation initiatives can also pose some challenges, as employees must adapt to new ways of working and the company culture must evolve to meet the demands of the new digital age.
Continuous Integration (CI) is the practice within software development that aims to detect source code integration errors sooner rather than later, enabling the development of stable code in a more expedient manner. The continuous cycle follows the pattern of phases that include: code, build, test, and deploy.