Likelihood to Recommend If you are truly using IBM API Management for an API gateway, you will be ok. if you start trying to build custom scripts to transform messages complex in nature, it will soon become unmanageable.
Read full review TV is well suited for high speed, which is a great for large tables. The workload functionality is very good when in Viewpoint. The BAR functionality could use a little work. QueryGrid is very useful as well. The client handlers are still a work in progress, as I keep hearing that they continue to fail. There are also many restarts on the systems as well.
Read full review Pros Import APIs - We have an existing inventory of APIs and services, so having an easy import process was required. IBM provides the ability to import Swagger so the process was quick and easy. Service Offerings - Can create plans to control various model offerings for varying clients depending on the need. You are not locked into a tier structure and can customize if a need arises. API Usage - visibility into the use of an API with a wealth of reporting information allows you to support an API from a production use to trending and forecasting any future growth. Read full review ETL (Extract - Transfor - Load) NOS to send data from Teradata Vantage to S3 and from S3 to Teradata Vantage Teradata GeoSpacial feature Bulk reading and writing in huge tables MPP capacity already mature Temporal Capacity more mature that other solutions TASM Read full review Cons Troubleshooting deployment pipeline - identifying issues with your api based on restrictions through a deployment pipeline is difficult. If a quality assurance environment is less stringent than a production environment, making sure your api is accessible and configured appropriately is tough. Code level scripting is limited to javascript and xslt. so if any complex fanning needs to occur, you are limited in tooling. Administration is more cumbersome than it needs to be. There are roles/profiles that are defined, but to use a group email for the approval or use of an api needs to managed better. A more thorough thought process needs to be defined - which I think IBM is tackling as an improvement. Read full review Teradata is an excellent option but only for a massive amount of data warehousing or analysis. If your data is not that big then it could be a misfit for your company and cost you a lot. The cost associated is quite extensive as compared to some other alternative RDBMS systems available in the market. Migration of data from Teradata to some other RDBMS systems is quite painful as the transition is not that smooth and you need to follow many steps and even if one of them fails. You need to start from the beginning almost. Last but not least the UI is pretty outdated and needs a revamp. Though it is simple, it needs to be presented in a much better way and more advanced options need to bee presented on the front page itself. Read full review Likelihood to Renew Teradata is a mature RDBMS system that expands its functionality towards the current cloud capabilities like object storage and flexible compute scale.
Read full review Usability It has helped our project to save time, effort and give accurate results in the quickest possible time. The diagnostics feature is also outstanding giving us a detailed report of the error which occurred, when it occurred and the likely cause and resolution of the same as well. The support of SQL is inherited which makes it easy to work on it because you don't need to learn any new language for this.
Read full review Support Rating We have meetings at the beginning with the technical team to explain our requirements to them and they were really putting in a lot of effort to come up with a solution which will address all our needs. They implemented the software and also trained a few of our resources on the same too. We can get in touch with them now as well whenever we run into a roadblock but it's very less now.
Read full review Alternatives Considered There are a lot of similarities between
Apigee Edge and IBM API Management. Some of the differences at the time of this posting is... 1) IBM APIM/C integrates better with other products. Dynatrace is used to track API and service specifics with the ability to offload those statistics for operational reporting. 2) If you are evolving from DataPower, IBM API Management is a logical choice to support additional REST APIs. 3) Generating keys is simple. Integration of those keys with a secure data vault is easy as well for your consumer.
Read full review Teradata is way ahead of its competitor because of its unique features of ensuring data privacy and data never gets corrupted even in worst case scenario. In most cases, the data corruption is a major issue if left unused and it leads to important data being wiped off which in ideal case should be stored for 3 years
Read full review Return on Investment Centralizing on an API management platform was imperative. Being able to support SOAP UIs as well as REST APIs was required. Because of the tooling, service inventory and provisioning can be managed - regardless of the pricing and cost structures are used. Constructing plans that provide tiering options based on rate limits help in onboarding new consumers. The lesser cost in onboarding through an API gateway outweighs the cost of modifying/configuring an API to handle multiple clients. Defining guidance and onboarding practices while rolling out the product also helps in the adoption, reference architecture, and governance that can save your company money. Read full review Saving time and cost through its stable integration tools which helps import and export a huge amount of different data. Providing analytics for the different data is easy and quick. Securing all the data processes across the entire company. Great Cloud solution for effective data quality management. Read full review ScreenShots Teradata Vantage Screenshots