rvsunilkumar

When designing data flows, choosing between pushing (sending data proactively) and pulling ( retrieving data on demand ) depends on factors like efficiency, latency, scalability and control.  Pushing Data: The source system sends data automatically to the destination as they occur. Pros of Pushing Data : Lower Latency: Updates are delivered in real-time or near real-time. Efficiency for High-Frequency data: Reduces the need for repeated requests when data updates frequently. Less Client-side Processing: The destinatiuon system doesn't need to monitor or poll for changes. Reduces Server Load (for clients). Eliminates unnecessary requests when no new data is available. Cons of Pushing Data: Potential Overload: if too much data is pushed once, the receiver may struggle to process it efficiently. More Complex Error Handling: if the destination is down, data might be lost without a proper retry mechanism. Requires Efficient Event Handling:  The destination must be able to hand...

MuleSoft Blog on PGP https://blogs.mulesoft.com/dev-guides/mule-pgp-encryption-gnugp/ There are eight processors related to PGP in Mulesoft , apart from PGP Global Configuration at this time of writing. 1. Pgp Encrypt 2, Pgp Encrypt and Sign 3. Pgp Encrypt binary 4. Pgp Decrypt 5. Pgp Sign 6. Pgp Sign binary 7.Pgp Validate 8. Pgp Binary to armoured. About Pretty Good Privacy (PGP)  In the context of Pretty Good Privacy (PGP) and its implementation GnuPG (GPG), key listings use specific abbreviations to denote different types of keys: sec : Secret (private) primary key ssb : Secret (private) subkey pub : Public primary key sub : Public subkey Key usage flags indicate the specific purposes for which a key can be utilized. These flags are represented by single-letter abbreviations: S : Signing C : Certifying (issuing certifications for other keys) E : Encrypting A : Authentication When you see a key with the usage flags SC , it signifies that the key is designated for both signing and...

 Refer Mulesoft blog link provided below  on how threading works in mule4, refer the scenarios presented for detailed understanding of different thread pools, switching and behavior. Broad Topics Covered: Centralized thread pools HTTP thread pools Thread pool responsibilities Thread pool sizing Thread pool scheduler assignment criteria Mule runtime example consumption of thread pools Typical thread switching scenario - usecases https://blogs.mulesoft.com/dev-guides/how-to-tutorials/thread-management-auto-tuning-mule-4/

 Here we will look at how Update SQL query with IN clause can be constructed when there are multiple values coming as array as IN clause input Assuming that dateSent must be updated for all the eventIds sent as input using IN clause. Input: { "dateUpdated" : "2025-01-14" , "eventId" : [ "234er-4356" , "234er-4896" , "4dse4-4321" ] } Building Update SQL in Dataweave %dw 2.0 output application/json --- { "dynamicUpdateStatement" : "Update table_name set dateSent='" ++ payload . dateUpdated ++ "' where eventId in (" ++ "'" ++ (payload . eventId joinBy( "','" ) ++ ")" ) } Output: { "dynamicUpdateStatement" : "Update table_name set dateSent='2025-01-14' where eventId in ('234er-4356','234er-4896','4dse4=4321')" } Screenshot: Another Solution: Dataweave: %dw 2.0 output application/json ---...

Salesforce SOAP API calls, Batch operations, and Bulk API v2 have specific purposes and use cases, especially when integrated with MuleSoft’s Salesforce Connector. Below is a comparison from the perspective of MuleSoft’s connector integration: Feature Salesforce Batch(SOAP call) Salesforce Bulk V2 Processing/API Type synchronous - Each call is processed immediately and waits for the result (suitable for real-time integrations). asynchronous - Operates asynchronously, meaning the request is submitted and Salesforce processes it in the background. The client does not wait for the completion of the operation. Record Limit Per call 200 Maximum number of records in a batch N/A (from v2 onwards), Maximum file size 150MB per Job, Maximum number of fields in a record 5,000, Maximum number of characters for all the data in a batch 10,000,000 Data Volume Best for smaller volumes of data (few records). Desi...

 Lets build to build file upload with MultiPart, below is RAML RAML /testUpload:      post:        description:  file upload to sftp        headers:         f ilePath:            description:  sftp file path            type:  string        body:          multipart/form-data:            properties:              fileName:                description:  file name                type:  string  ...