AWS OpsWorks is a configuration management service that provides managed instances of Chef and Puppet.
N/A
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
MindTouch
Score 7.0 out of 10
N/A
MindTouch is a customer experience management platform with content management and help authoring capabilities. Formerly known as MediaWiki, it is optimized for building knowledge bases for customer self-service and agent assistance purposes.
Opsworks will become EOL soon and we have been using the recommended Systems Manager solution recently which offers a lot more flexibility in terms of orchestration technology (ie. higher Chef versions) and easier to integrate with even more AWS services.
We first got up and running with OpsWorks about 6~7 years ago, at a time when many of its competitors were far more limited. At the time it made sense as the logical tool to go with and getting up and running on the AWS infrastructure was beneficial for the scale we were …
OpsWorks isn't really a direct competitor to Terraform/Cloudformation, but it does allow you to do some of the more simple things on offer quite quickly and effectively. Opsworks was used for this reason, along with existing internal knowledge of Chef. Along with some of the …
AWS CDK is like a cloud-specific alternative to Terraform. As its name suggests, it's from AWS & only works with AWS, a job it does excellently. If your cloud provider is not AWS, then you really only have Terraform to choose. If you are on AWS, it boils down to which one you …
IBM Terraform is better as the providers just work. Ansible is still finicky with their community modules for cloud, especially for Azure. We do not need to build execution environment containers like Ansible. Using statefil for drift analysis is also helpful to review changes …
Dbt was fine, but you end up with an extremely bloated repo/project. Often where all of the models are the same, named similarly, and generally just doesn't adhere to the concept of DRY coding. In Terraform we're able to template a lot of this work and dynamically generate …
HashiCorp Terraform is much better than Cloud Formation. For one, the language is just easier to use, but more importantly, the provider ecosystem is much better in HashiCorp Terraform than in Cloud Formation.
I'm beginning to look at Pulumi. In my opinion, it looks like it would be a good replacement for HashiCorp Terraform, and it has the advantage of configuration via scripting, rather than via HCL, which is HashiCorp Terraform configuration markup language. In my opinion, the …
We have used Vagrant to develop our application in a virtual box environment and prepare it to be packed with Packer. The image created from these two tools will be deployed by Terraform.
We are using Consul for service discovery and as a job locking so we don't have two jobs or …
CloudFormation is only for AWS so if you're trying to deploy to another cloud provider then Terraform is your product. Terraform has lots of public support so you can find answers to questions by Googling. CloudFormation is easy to view the resources/services that are …
Terraform is a large step ahead of the previous generation of infrastructure-as-code providers. I'd never go back to, e.g. Puppet or Chef, Ansible, etc. That said I think that Pulumi has a good chance of displaying it, in no small part because the Terraform language itself …
AWS CloudFormation is better if you just want to stick with AWS because it's integration with AWS is better, provides auto-rollback in case of failures, and has GUI to manage and view the stacks built. Terraform is better when we want to stay cloud-agnostic. Terraform is better …
I can't find these applications listed, but other IaC tools I have used include: AWS CloudFormation, Azure Resource Manager Templates, and GCP Cloud Deployment Templates. For a comparable tool, I have the most experience with CloudFormation.
Chef and Terraform are not apples to apples because Chef is more focused on config management, whereas Terraform is more focused on provisioning. However, I can say that where they do overlap in configuration management is that Terraform is the preferred tool because it has an …
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 …
Terraform is open source and has strong community support. It is cloud-agnostic versus competing products like AWS cloud formation, hence has a distinct advantage. The scripts once set up are easy for developers to administer during development, hence during production …
- Terraform syntax is much easier to read and learn than Cloud Formation.
- Terraform already supports AWS as well as several other cloud providers.
- Terraform is backed by a great and supportive open-source community.
Terraform shares the methodology of creating configuration files for your infrastructure with tools like CloudFormation. However, Terraform is cloud-agnostic unlike CloudFormation which is AWS specific. Terraform can be used to maintain AWS and OpenStack clusters …
CloudFormation is the lingua franca of AWS. You certainly can't go wrong using it, but I like the syntax and open-source nature of Terraform. That's mostly a personal preference. I have not tried any other non-Amazon tools for provisioning AWS. And, of course, the AWS tools …
I will be brief. DealerTeam is built upon Salesforce and we try to support native apps. We used Desk.com first for basic Help Ticket management. The product did not satisfy how our customers were looking for information. We upgraded to Service Cloud with Knowledge Base and …
MindTouch wasn't the cheapest option we considered, but it was the best value. It gave us the most features, controls, flexibility, and growth opportunity for the money we paid for it. We did not need a ticketing solution, and a lot of the offerings we evaluated were stronger …
In my view, MindTouch is hands down the industry leader when it comes to documentation and publishing products. None of the other products I have used provide such an intuitive interface for single-source content creation. MadCap Flare has a steep learning curve and requires …
Actually, when we evaluated MinfTouch it was evident that we didn't really need to perform due diligence against other solution providers. It was apparent from the get-go they were the perfect fit for the problems we were trying to solve.
We selected MindTouch after being given assurances it met all of our needs. Whilst I am sure it can do this, it was not made apparent the technical ability required to be able to achieve this and given the choice again we would not have selected MindTouch.
Each suite offered a variety of features; however, MindTouch had powerful SAP integration and as a hosted solution the value of ownership was nearly immediate. Put on top of the API and CSS options for customization MindTouch was the top solution for our documentation …
MindTouch offers a unique knowledge and information management tool that was different enough from traditional knowledge bases and advanced enough to not be a Wiki while allowing CRM integration and APIs for customization. MindTouch as a company is focused on making their …
We were on Salesforce.com's KB and did not like the interface and the difficulty with article creation. The advantage of SF was that we could assign articles to individuals for review. I feel that is missing with MindTouch. It makes article creation workflows very difficult.
I did not select MindTouch at my current company, but I was looking into it at my previous position. It has many of the useful features of the more traditional publications tools (RoboHelp, Frame) with the ease of web deployment of other tools (HelpIQ). It has some limitations …
We selected MindTouch because: - it could support multiple products inside of one instance - it could support both external and internal users with conditionalized access to content
We previously used MadCap Flare. Flare is amazing for its single sourcing capabilities, where MindTouch is lacking. But with Flare we had to do an entire build and publish each time (which took hours).
We looked at Happy Fox, Salesforce Communities, Fuze, MadCap Flare, etc. MindTouch won out because of its Salesforce integration and the fact that it was a hosted solution with everything included in one price.
N/A. It has been several years since I evaluated competitors. I'm vaguely aware of ZenDesk and am in process of evaluating not - not with the intention to replace MindTouch, just to keep up with trends in the industry. I would consider a move if I ever felt that MindTouch was …
MindTouch has a high degree of user freedom regarding customization, offers a quick-responding support team, and keeps their site up-to-date and modern. The combination of these abilities made MindTouch a fine choice that could suit our needs.
We evaluated various knowledge base options and previously used a home-grown site for documentation. Mindtouch had more options than we knew were possible and provided a more robust product.
We used Parature a long time ago but we left that system due to increasing costs and we moved to SFDC and WordPress. For a few years we used WordPress which was very difficult to manage especially for managing images, page redirects and overall longterm maintenance of content.
MindTouch is not as sophisticated as those editors but MindTouch is the only one that generates HTML. The other editors provide additional, advanced functionality, are more bulletproof, and require the services of an experienced technical writer. MindTouch, however, is simpler …
AWS Opsworks is good for linking AWS services and setting up and maintaining webservers using Chef. However, it will become EOL soon so we would not recommend starting new projects using it and instead go for the recommended Systems Manager setup
8 because it's currently best-in-class and is completely essential to use in contrast to not expressing your infrastructure as code. That said, new contenders are nipping at its heels, and I expect stronger tools to emerge in the coming years. Hopefully the Terraform team is able to keep pace.
I would recommend MindTouch to anyone who is looking to create and host their documentation for a product that has multiple types of users. Our business modal represents customers on the buy-side as well as the sell-side and we are able to easily organize documentation to service both types of users.
The interface is quite intuitive and allows you to discover and easily find what you want to do and what other features are within OpsWorks.
Chef integration is pretty seamless and there are a good set of options and operating systems to choose from
It makes things like auto scaling set up, either via load or time, more straight forward and intuitive than what you'd typically see via the EC2 console
Good privacy settings for each page. I can set a new article to semi-private until it's approved to go live. And I can send a link to that page out for review.
Good tracking on each page history.
Ability to view and restore previous page versions.
I like the category search bars that only search the current category.
The errors generated by the plan and preview commands are pretty cryptic, it can be hard for newcomers to the scripting language to understand how to address problems.
Access controls around workspaces is limited which makes it harder to secure reduce the scope of teams ability.
Analytics around user usage, applies and plans would be helpful for managemenet.
User experience. The product's UX is fragmented and it's hard to figure out how to do some certain very simple, important things.
Many aspects of the product don't really meet industry standards for technical communication. They seem to have been cobbled together by people who don't fully understand what technical writers do. Product updates really don't address these issues. Folks in sales and support sometimes imply that the authoring platform MindTouch has created is the only way to do create documentation, which is counter to the experience of those of us who've been in the industry for any length of time.
We've put lots and lots of content into the MindTouch system, of course, so that makes it harder to opt out, but we're also very pleased with their rate of development and weekly pushing of improvements, as well as their response and solutions to our questions and input All in all, a winning combination.
The syntax itself is pretty straightforward. The documentation is well-maintained & easy to follow. Most cloud providers, even smaller ones, maintain official provider libraries, making discovery & learning a breeze. Some, like GCP, even provide high-level libraries on top of their own more primitive provider, making building complex infra much more manageable. The language itself is cloud-agnostic, so you can literally manage resources from multiple providers in a single Terraform repo.
MindTouch has many formatting options but some procedures (like editing a template) are not easy to figure out. We needed to create several custom templates for our content and found the MindTouch user documentation on this process somewhat contradictory and incomplete.
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.
MindTouch is a hosted site, so as a heavy user there are times when I notice that pages are slow to load, or something happens like Amazon Web Services crashing the entire east coast for a few hours, that you do notice even if it isn't actually the fault of the MT tool itself. It's the risk of using a hosted tool, but the benefits are pretty amazing and outweigh these performance issues.
Unless you pay for a pricey support package getting support on OpsWorks will be pretty slow. Documentation is also relatively limited and sometimes hard to follow when compared to competitors. Generally, we've been able to get the answers we need from OpsWorks support when we run into problems but don't expect rapid responses.
Terraform is community driven but does offer support for it's Enterprise product. When contacting the team at HashiCorp we have always gotten resolution to our issues. They have been very responsive in returning our calls and answering our questions as they come up. We are currently using the open source model.
Mindtouch support is awesome. Support agents are friendly and helpful. Some can benefit from ongoing training. Overall the support experience is very good. One area they can possibly improve is visibility into product feedback. Seeing or getting insight into requests or votes for features would be an added customer experience.
Written documentation and videos are very good and have helped on numerous occasions when I've had to look up how to accomplish a certain task. The reason I have not given a full score is mainly because there have been some inaccuracies in the documentation because updates to the MindTouch framework have slightly changed the way things work. But this is usually the same type of challenges I face when making documentation for the software solution we develop. So all in all I'm very satisfied with both the personal webinars and the online documentation MindTouch provides for their service.
Just know that there is so much more involved than adding your content. There are so many pieces to launching your site -- especially if you are moving from another platform. If you are not a person who typically works in the "website" realm, do your homework, ask your web people, engineers, etc., because there's a lot to do that you won't know about until you are unexpectedly smacked in the face with it. Learn from my mistakes! We are very happy now, but it was a long road getting to launch day for us
OpsWorks isn't really a direct competitor to Terraform/Cloudformation, but it does allow you to do some of the more simple things on offer quite quickly and effectively. Opsworks was used for this reason, along with existing internal knowledge of Chef. Along with some of the other services on offer from AWS, it is good to use as a stepping stone along the way when building your systems - or perhaps it would be entirely suitable for a fairly simple project.
dbt was fine, but you end up with an extremely bloated repo/project. Often where all of the models are the same, named similarly, and generally just doesn't adhere to the concept of DRY coding. In Terraform we're able to template a lot of this work and dynamically generate assets based on variables instead.
I will be brief. DealerTeam is built upon Salesforce and we try to support native apps. We used Desk.com first for basic Help Ticket management. The product did not satisfy how our customers were looking for information. We upgraded to Service Cloud with Knowledge Base and spent one year writing content and developing our support agency. Again, our customers were upset about submitting help tickets and waiting for answers. They wanted access to self-help while working with a customer. Today we continue to use Service Cloud with MindTouch integration and have found complete success. There is simply no other solution I know of that is a flexible and easy to use as MindTouch when it come to providing customer success and product support
OpsWorks allowed us to access the AWS infrastructure with a considerably lower time investment than we would have otherwise needed when we first implemented it.
Since we've been running with OpsWorks we've experienced very little downtime and it's required relatively little maintenance.
The main downside of using OpsWorks for us is that it has locked us into a very specific infrastructure that doesn't have the flexibility of many of the newer infrastructure management tools, this may lead to a painful migration down the road. We also run a risk of long outage if it ever does introduce breaking changes as the skillset needed to work with the OpsWorks tooling is very specific not widely available in our company.
Using code, we are able to build and deploy cloud resources faster and more consistently than producing the same resources in the console manually.
For applications that share architectures, we can reuse code to expedite development. We can also do the same with modules that are shared across the organization.
By defining all of our resources as code, we can deploy complete environments with "batteries included." For example, we can use code that spins up servers in a cloud provider and at the same time, creates monitors with in our monitoring provider. Likewise, when the servers are decommissioned, the monitors are decommed along with them. In the past, the creation and decom of the monitors would have been a disjointed, manual step. With Terraform we get it all with one "terraform apply."
Time to publication can be very quick, provided there are not multiple changes in flight at the same time for the same page.
We have seen a tremendous increase in customer traffic and SEO.
MindTouch allows us to custom-brand the look and feel of our site to match our company's marketing and branding. This instills trust in our content.
The relative simplicity of the platform enabled us to hire the best people and best writers we could find, without worrying so much about specific past expertise in a complicated publishing platform.