cancel
Showing results for 
Search instead for 
Did you mean: 

What will be the best integration solution

CodersArcade
Deputy Chef II
Deputy Chef II

Our goal is to establish Integration A, which serves as a data repository. The data stored in Integration A is then utilized in another recipe, Integration B, to ascertain the appropriate endpoint for data transmission. What is the most effective method to accomplish this within Workato? The current proposal involves storing data in a lookup table. Are there any superior alternatives or recommendations

1 ACCEPTED SOLUTION

Because it doesn't share the same limit as a Lookup table.  While the Lookup table maxes out at 10,000 records, aI'm not aware of a limit to the number of messages stored in a Pub/Sub Topic.  It's essentially a message queue so it's designed to hold many messages to be consumed.

View solution in original post

4 REPLIES 4

bkramer
Deputy Chef I
Deputy Chef I

Just be aware of the limitations of lookup tables:

  • Has a maximum of 10 columns
  • Has a maximum of 100,000 entries
  • Individual columns have a character limit of 100,000 characters

mppowe
Executive Chef I
Executive Chef I

@bkramer makes a good point about Lookup tables.  If you need more scalability, some other options could be publishing the data as Topics to a Pub/Sub integration pattern (which Workato has natively).  You could also create a CSV to store in Workato FileStorage that Integration B reads (perhaps the file path is stored in your lookup table).  There's also Workato Table Storage though I haven't looked at that yet, and I want to say it might be connected to Workflow Apps.

How would a pub sub or topics help in the above said integration?

Because it doesn't share the same limit as a Lookup table.  While the Lookup table maxes out at 10,000 records, aI'm not aware of a limit to the number of messages stored in a Pub/Sub Topic.  It's essentially a message queue so it's designed to hold many messages to be consumed.