Panoply vs. WSO2 Integration Platform

Panoply is well suited for companies with large amounts of data that do not want all users of the company to see or view. It is appropriate for companies that have to store data for several years in case clients need the data. It is not made to constantly be downloading or looking at the documents.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

The best-suited scenario is the service chain pattern or all patterns used in online mode. The less appropriate scenario is a batch service the duration time of the service is more than 10minutes because it is necessary to increase the HTTP timeout.

• Ease of data integrations. Importing data into the data warehouse is a point-and-click effort.
• Automated data modeling. The data is modeled in a way that facilitates analysis without having to look into it myself.
• Query speed. Automated query optimization has really sped up our dashboards.

• Service chain pattern
• Message transformation
• Call more than one backend service
• Call service with different protocoll as the client use
• Use file as input
• Use mail as input

• The user interface could use some improvement for analytical tools. Apart from that, it’s great.

• View deploy artifact in date time order
• Easy way to map data
• Easy way to manage payload

It’s a good choice for building a quick, multipurpose data stack for a variety of businesses needs.

Panoply has much more storage and better organization tools for searching. There are better folders and tools for keeping documents secure and stored for a long period of time. It is better to offload data in mass than singular or Zip drive documents like you would do in Google Drive.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

We can start with the community version and then when we moved into production we can buy the supported version. The supported and community version have the same code so we can do every test before deciding to buy the supported version.

• Saved time on Redshift setup
• Saved support costs (monetary and temporal) by not having to set up on-premise
• Widens the BI tool use in organization; lowers the barrier to entry and makes organization more productive in analytical terms

• Reduce development time to the service integration
• We can use junior developer
• Clustered in easy way