Alooma vs. webMethods.io Integration

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Alooma
Score 9.0 out of 10
N/A
Alooma is a data integration product providing ETL capabilities with a focus on output to data warehouse. It also offers pipeline monitoring and error handling protocols.N/A
webMethods.io Integration
Score 9.0 out of 10
N/A
webMethods.io Integration (formerly webMethods Integration Cloud) from Software AG is designed to make it easy to connect SaaS apps and make business processes more efficient. It enables enterprise subject matter experts and eliminates integration silos, allowing users to integrate applications hosted in public or private clouds, as well as applications hosted on premises.N/A
Pricing
AloomawebMethods.io Integration
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
AloomawebMethods.io Integration
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
AloomawebMethods.io Integration
Top Pros
Top Cons
Features
AloomawebMethods.io Integration
Cloud Data Integration
Comparison of Cloud Data Integration features of Product A and Product B
Alooma
7.5
1 Ratings
8% below category average
webMethods.io Integration
7.7
1 Ratings
5% below category average
Pre-built connectors8.01 Ratings8.01 Ratings
Connector modification7.01 Ratings9.01 Ratings
Support for real-time and batch integration7.01 Ratings8.01 Ratings
Data quality services8.01 Ratings7.01 Ratings
Data security features7.01 Ratings7.01 Ratings
Monitoring console8.01 Ratings7.01 Ratings
Best Alternatives
AloomawebMethods.io Integration
Small Businesses
Make
Make
Score 9.3 out of 10
Make
Make
Score 9.3 out of 10
Medium-sized Companies
Zapier
Zapier
Score 8.9 out of 10
Zapier
Zapier
Score 8.9 out of 10
Enterprises
Azure Logic Apps
Azure Logic Apps
Score 8.9 out of 10
Azure Logic Apps
Azure Logic Apps
Score 8.9 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
AloomawebMethods.io Integration
Likelihood to Recommend
8.0
(1 ratings)
9.0
(1 ratings)
User Testimonials
AloomawebMethods.io Integration
Likelihood to Recommend
Alooma
Very appropriate for managing an ELT stack -- Alooma handles the 'E' and 'L' pieces very well. Due to the way transformation is setup, it is more on the lightweight side of things and thus works for this kind of stack. For more traditional ETL stacks, Alooma would probably not be the right fit.
Read full review
Software AG
We don't use webMethods.io Integration for scenarios where we need to integrate to on-premises legacy applications that have limited support for modern security controls such as OAuth 2.0 and transport encryption. Likewise, we don't use it for solutions that involve any of our systems that are controlled by safe-working processes. For those scenarios, of which we have many, we maintain on-premises webMethods Integration Server and Trading Networks instances to build and execute and support and monitor those solutions. This then requires us to hook our on-premises integration platform up to the webMethods.io Integration cloud, to ship messages between the two integration platforms. This all begs the question if a cloud solution cannot be used for all use cases or scenarios that the business has, then why add the complexity of using the cloud at all if you still need to maintain an on-premises solution to support the non-cloud appropriate scenarios.
Read full review
Pros
Alooma
  • Transformation of data before entering the data warehouse -- allows for a consistent/understandable schema for analytics teams.
  • Adding of additional data sources: Alooma has a large library of pre-built, common 3rd party vendors for which data is often needed to be ETL-ed.
Read full review
Software AG
  • Easy to use
  • Priced competitively
  • Supports robust and resilient integration solutions
Read full review
Cons
Alooma
  • More tools on managing the data warehouse itself. Although great on the ingest and transformation of data, more help provided by the tool on managing the outputs would be welcome.
  • Increase possibilities in the transformation step, rather than single event transformations.
Read full review
Software AG
  • Complex logic is hard to understand in simple diagrammatic user interface
  • User interface too simplistic for solutions that are complicated or go against the grain
  • Runtime observability could be improved
Read full review
Alternatives Considered
Alooma
Haven't used the alternatives, since Alooma was one of the earlier ones to the market. From a cursory viewing, however, the features seem to match relatively similarly.
Read full review
Software AG
webMethods.io IntegrationDescriptionWe uses webMethods.io Integration to solve some of our application to applications and business to business integration needs. It is the Integration Platform as a Service solution that we use in a mix with our continued use of webMethods Integration Server and Trading Networks on-premises. For any solutions that meet the use cases that we deem an appropriate fit for running in the cloud, we build those solutions using webMethods.io Integration. More specifically, we use webMethods.io Integration to synchronize changes in one application or system, in another application or system, by shipping data mutations via integration messaging and API calls. We also use webMethods.io Integration to integrate with external organizations. Our trading partners and supply chain partners provide APIs that we consume, and vice versa, to notify each other of business process events as they occur in the respective organizations. Please provide some detailed examples of things that webMethods.io Integration (webMethods Integration Cloud) does particularly well. Easy to usePriced competitivelySupports robust and resilient integration solutions please provide some detailed examples of areas where webMethods.io Integration (webMethods Integration Cloud) has room for improvement. These could be features that are hard to use, missing functionality, or just things that you'd like to see done differently. Complex logic is hard to understand in a simple diagrammatic user interface too simplistic for solutions that are complicated or go against the gain runtime observability could be improved please describe some specific scenarios based on your experience where webMethods.io Integration (webMethods Integration Cloud) is well suited, and/or scenarios where it is less appropriate. We don't use webMethods.io Integration for scenarios where we need to integrate to on-premises legacy applications that have limited support for modern security controls such as OAuth 2.0 and transport encryption. Likewise, we don't use it for solutions that involve any of our systems that are controlled by safe-working processes. For those scenarios, of which we have many, we maintain on-premises webMethods Integration Server and Trading Networks instances to build and execute and support and monitor those solutions. This then requires us to hook our on-premises integration platform up to the webMethods.io Integration cloud, to ship messages between the two integration platforms. This all begs the question if a cloud solution cannot be used for all use cases or scenarios that the business has, then why add the complexity of using the cloud at all if you still need to maintain an on-premises solution to support the non-cloud appropriate scenarios. What positive or negative impact (i.e. Return on Investment or ROI) has webMethods.io Integration (webMethods Integration Cloud) had on your overall business objectives?webMethods.io Integration is a cost-effective approach to integration in isolationwebMethods.io Integration as a supplement to on-premises integration is pointless and redundant and just adds complexity to the environment and additional costswebMethods.io Integration is a tough sell for organizations using Microsoft Azure integration products such as Logic AppswebMethods.io Integration has a faster time to market where the use case means standard provided adapters can be used describe how webMethods.io Integration (webMethods Integration Cloud) stacks up against them and why you selected webMethods.io Integration (webMethods Integration Cloud). For any organization which is already using Software AG products on-premises, such as webMethods Integration Server and Trading Networks, or Universal Messaging, evaluating and using webMethods.io Integration is the path of least resistance. It will be incredibly easy for your webMethods team to get up to speed on how to use webMethods.io Integration, and start developing new solutions on it. However in my opinion you should only add cloud to your integration product portfolio if you believe you can move 100% of your integration needs to the cloud. Otherwise, you will need to maintain an on-premises integration solution anyway, which means you end up with a more complex IT landscape by adding cloud to supplement on-premises integration for little benefit in terms of cost, complexity, and resourcing requirements. For organizations that are not already a Software AG shop, you should evaluate webMethods.io Integration on its merits, however, it's usually the right decision to double down on your existing products and vendors if you have no big issues with the current state. This is to say that if you are a Microsoft shop then adding Azure cloud products to your portfolio is pretty much inevitable, and avoiding the complexity of multiple clouds should also be something organizations consider.
Read full review
Return on Investment
Alooma
  • Allowing for additional data sources to more automation capability around monitoring the business is a huge ROI
Read full review
Software AG
  • webMethods.io Integration is a cost effective approach to integration in isolation
  • webMethods.io Integration as a supplement to on-premises integration is pointless and redundant and just adds complexity to the environment and additional costs
  • webMethods.io Integration is a tough sell for organizations using Microsoft Azure integration products such as Logic Apps
  • webMethods.io Integration has a faster time to market where the use case means standard provided adapters can be used
Read full review
ScreenShots