cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Have you ever used Integration Patterns in Workato to solve a problem?

tanguyaerts
Deputy Chef I
Deputy Chef I

Hi!

I have a background in game development where OOP and its patterns are central to a good solution. Recently, I've been hired as a Junior Integrations Engineer where I'm learning to work with Workato. Naturally, I gravitated towards the usage of patterns and started reading Enterprise Integration Patterns. This leads into my question: have you ever used integration patterns in your recipes? I'd like to be sure that these patterns can be applied in Workato recipes before I read the entire book.

Thank you for your time!

3 REPLIES 3

mppowe
Executive Chef II
Executive Chef II

I think integration patterns certain apply to Workato, yes.  The book seems a bit old as it says it was published in 2003.  I'm sure parts of it still apply but there may be more up-to-date resources out there.  But the concepts it mentions like asynchronous processing and messaging systems still apply and will be good to understand as you build out integrations within and around Workato.  Bulk processing (rather than always handling transactions one at a time), SOAP vs REST API connections, and  understanding the Publish/Subscribe pattern will also be good concepts with which to familiarize yourself

Hope that helps

Thanks for the answer!
I agree on the concepts you listed. Those are important and I've used them often. However I was actually referring to the patterns within the book like the 'Message Router' and 'Control Bus' pattern (apologies, I should've included them). Those patterns are definitely useful in a software engineering setting but I'm unsure if Workato provides enough tools to build such generic solutions like 'Message Routers'.
Thank you for your help!

In glancing at those topics, I suspect you could build your own version of it within Workato but I haven't had the need to.  Workato has a built-in message queuing system ("Event Streams" as it's now called), and if, for some reason that couldn't cut it, there are a lot of other options to provide those capabilities (eg RabbitMQ), so I'm not sure I'd want to undertake manually creating those components/systems, whether inside Workato or out.  I'm not saying there's no Use Case or justification for it... just haven't run across it myself.