Summary

As our technology landscape continues to evolve, so will the latest and greatest formats for communicating and sharing data. It feels like just yesterday that service-oriented architecture was going to change our world using SOAP messages and WSDLs. Then, just as we all got our service converted to facilitate the use of SOAP messages, it became RESTful services and JSON was all the rage. It would be extremely difficult to keep up with these technology and architecture shifts with all of our applications and systems; however, we will need to expose our legacy service to our modernized consumers using the latest and greatest. This is where the power of message transformation comes into play.

You have seen how we can easily transform our message from one format to another, or enrich the data as it comes in. You have also seen how API Connect provides built-in policies for some very specific use cases and transformations, making it a simple drag and drop configuration. Of course...