ER/Studio is a database development and management tool from Embarcadero Technologies (acquired by Idera) in California.
$2,687
per year per user
IBM Terraform
Score 8.8 out of 10
N/A
IBM Terraform (formerly Hashicorp Terraform) is a cloud infrastructure automation tool used to create, change, and improve production infrastructure, and it allows infrastructure to be expressed as code. It is available Open Source, and via Cloud and Self-Hosted editions.
$0
Pricing
ER/Studio
IBM Terraform
Editions & Modules
Standard
$2,687
per year per user
Professional
$3,693
per year per user
Enterprise
Custom
per year per user
Open Source
$0
Team & Governance
$20/user
per user/per month
Enterprise
Contact sales team
Offerings
Pricing Offerings
ER/Studio
IBM Terraform
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Pricing for new customers only, first year maintenance included. Maintenance includes access to technical support and product updates for the defined period of the agreement.
Data Architect is well suited at organizations of all sizes. It is never too early or unnecessary to enforce proper modelling and design standards on data solutions, and this tool will help that greatly by providing an industry leading data modelling tool, ability to import ETL mappings for data lineage, enforcing and managing naming conventions through the naming convention tool, and publishing of data dictionaries through the report publisher. I was successfully able to build models, provide traceability, and document source to target with lineage throughout for both the business (by providing business definitions in the descriptions), and technical teams (by documenting ETL instructions in text fields) along with field level mapping (by creating "Attachments" representing data sources, tables, and fields) providing easy search capabilities using business friendly terms
Anything that needs to be repeated en masse. Terraform is great at taking a template and have it be repeated across your estate. You can dynamically change the assets they're generating depending on certain variables. Which means though templated assets will all be similar, they're allowed to have unique properties about them. For example flattening JSON into tabular data and ensuring the flattening code is unique to the file's schema.
ER/Studio has the ability to provide consistent field names and data types through domains, which are templates. This provides a way to have consistent naming of common fields, like CreatedBy and the data types for the fields. They also have the ability to change all the fields that use that domain to a different data type.
ER/Studio provides the ability to create custom macros. These macros can be used to apply everything from standard fields based on domains to naming all constraints and indexes. I've also used a macro that comes with ER/Studio to spell check field and table names.
My favorite feature is the ability to compare your data model to databases for deployments of changes, and to other data models.
ER\Studio licensing can be cumbersome and upgrading from one version to another usually takes several phone calls and emails to the licensing group to get the update installed and running.
The repository can be slow when the model count gets larger. By large I mean 20 to 30 models.
A nice feature that I would like to see is table comments be displayed on the model along with the attributes. Currently you have to choose between the two.
The language itself is a bit unusual and this makes it hard for new users to get onboarded into the codebase. While it's improving with later releases, basic concepts like "map an array of options into a set of configurations" or "apply this logic if a variable is specified" are possible but unnecessarily cumbersome.
The 'Terraform Plan' operation could be substantially more sophisticated. There are many situations where a Terraform file could never work but successfully passes the 'plan' phase only to fail during the 'apply' phase.
Environment migrations could be smoother. Renaming/refactoring files is a challenge because of the need to use 'Terraform mv' commands, etc.
I love Terraform and I think it has done some great things for people that are working to automate their provisioning processes and also for those that are in the process of moving to the cloud or managing cloud resources. There are some quirks to HCL that take a little bit of getting used to and give picking up Terraform a little bit of a learning curve, thus the rating
Terraform's performance is quite amazing when it comes to deployment of resources in AWS. Of course, the deployment times depend on various parameters like the number of resources to deploy and different regions to deploy. Terraform cannot control that. The only minor drawback probably shows up when a terraform job is terminated mid way. Then in many cases, time-consuming manual cleanup is required.
I can call or email support and both get quick turn around. The only issue is they are on the west coast (US) and have a west coast work schedule and I'm on the East coast.
I have yet to have an opportunity to reach out directly to HashiCorp for support on Terraform. However, I have spent a great deal of time considering their documentation as I use the tool. This opinion is based solely on that. I find the Terraform documentation to have great breadth but lacking in depth in many areas. I appreciate that all of the tool's resources have an entry in the docs but often the examples are lacking. Often, the examples provided are very basic and prompt additional exploration. Also, the links in the documentation often link back to the same page where one might expect to be linked to a different source with additional information.
Terraform is the solid leader in the space. It allows you to do more then just provisioning within a pre-existing servers. It is more extensible and has more providers available than it competitors. It is also open source and more adopted by the community then some of the other solutions that are available in the market place.
ER/Studio has had a positive impact on my project as we can develop the data model and have a clear understanding of business needs before we continue with the development phase.
we are able to deploy our infrastructure in a couple of ours in an automated and repeatable way, before this could take weeks if the work was done manually and was a lot of error prone.
having the state file, you can see a diff of what things have changed manually out side of Terraform which is a huge plus
if state file gets corrupted, it is very hard to debug or restore it without an impact or spending hours ..
writing big scale code can be very challenging and hard to be efficient so it's usable by the whole team
