In this technology section of the blog I hope to distill some useful ideas from many the notes I’ve collected over time and present a comprehensive (and hopefully coherent) set of patterns and utilities that are still of use.
Due to the rapid pace at which technology morphs and deprecates earlier generations, this may be too daunting a task. Bucking the headwinds, as change occurs, i’ll do my best to adjust where it makes the most sense. You can find some of these earlier works in my other writings in DZone and Medium. A brief synopsis of each follows below.
Articles i’ve published on other sites
Learn how you can use the Dataweave CLI (DW CLI) to map and transform: XML, JSON, CSV, Text, YAML and Properties to name but a few. The DW CLI is a command line tool for creating pipelines of information between data sources and data sinks. To learn more check out my article Transformative Moments.
When using DataWeave to transform your messages you will begin to realize common integration patterns across your projects. Following the principle of DRY (don’t repeat yourself) we’re working on capturing them in the Dataweave Cookbook.
Maybe next time you’re in need of an integration pattern you can find it in the cookbook.
Looking for a RESTful mocking solution? In Zero Code REST with json-server we present a solution to get you up, running and productive at warp speed. Get a Clue extends the possibilities by Dockerizing the static data set. Read on, if you have a need to provide Basic Auth Security to you Mock.
A popular read for those of you getting started with GO and database interactions – Better practices for Go Database use.
In some of my other articles on Kubernetes, we take a look at what’s happening at the IOT edge of computing.
If you’re just getting started with Mule 4 and would like a better understanding of how to get your feet wet with DataWeave 2.x, check out the DataWeave playground.
In Dockerize your Mulesoft API’s we discuss an approach for running your Mule 3.x API’s in containers. In 4.x Mule now has a home grown approach for providing the same, though the earlier solution may still prove to be more loosely coupled.
Spring Cloud config with the Mule ESB is another 3.x artifact which may have outlived it’s usefulness. The concept of externalizing properties which are discoverable at startup is still a good one, but this pattern is broken in 4.x. Perhaps if there’s enough interest I may look at porting into the current connector paradigm.
Using Jolokia and HawtIO explores hooking an Open Source JMX instrumentation stack into the Mule. This may be useful if you have the need to change behaviors at runtime (such as debugging levels). You might also be interested in this simple tolling for converting Swagger into RAML.
Interested in simple tools for measuring network latency? Consider giving httping a try.