One of my co-workers asked this week about best practices for documenting applications developed for a client project.
As I started compiling guidelines coupled with my experiences, it grew long enough to be its own blog post.
So I share it here for everyone to read.
I see unit tests to be returning contents that exactly match the intent. JsonUnit was very helpful when I was working with Mule 3 but this time I wanted to get the default matchers (MUnit 2) available in Mule 4 to work
This week, I was designing a queue monitoring solution in the simplest possible way I could to alert users via email.
One of the programming tasks was to determine the time elapsed from last 6 hours (for example).
I used Mule 4's Scheduler component, a near replacement to Poll scope …
Development of REST APIs and enterprise integration patterns in Mule has the advantage of being able to quickly implement commonly required functionality. Its set of drag-and-drop and quickly configurable connectors make the implementation faster
when compared to writing boilerplate code
However when you need connections to be made to a …
I was working on adding backend flexibility capability to an otherwise H2-backed application developed in Mule 3 when the request to move it to Mule 4 came up. The user would be able to configure the application to run with any of the 6 database backends supported by altering …