11:11 Public Cloud vs. AWS CloudFormation

When shared with multiple teams, I could not find many products better than this. I enjoyed working in this aspect, it was smooth in cross-teams transferring. They have a good foundation of technology I would say, the thing it is lacking is in the usability for non-technical people. I have seen many struggling with this aspect.

Incentivized

AWS CloudFormation is well suited for scenarios where all of your resources need to be provisioned on AWS but it is not suited for hybrid cloud deployments. It's very easy for someone new to learn. The level of customization offered as part of the template specifically for AWS services is great. There is also a UI tool where we can drag and drop the services we want and it generates an yaml file which is very easy to use. The visibility of stacks and its resources and one place where we can track and identify the issues in deployment is great.

Incentivized

• Security - no-one can access your systems, even you!

• SaaS
• Paas
• Iaas
• On promises

Incentivized

• I needed support for many modules, where I think I was not satisfied.
• The detailing of each module is lacking.
• If you form clutter of files, there is no solution for it.

Incentivized

• Error Description upon Failure Needs to be Improved.
• Slow to create, delete or update.
• Need to delete resources manually. It can ask before starting deletion whether to skip those resources or delete them.

Incentivized

Support is completely inflexible in their policies and procedures, turning even the simplest request into a months-long ordeal.

I would select Sungard on the basis of technology foundation and functionality. It gave me an ample amount of features which I could use in a better way. The inter-team communication gets a better structure than the other products. I would use it on the basis of the above mentioned points. This has proven to be a good support for my team.

Incentivized

We didn't look into anything else as Cloudformation was "built-in" for AWS, it just kind of made sense to go with that. Terraform was something that we briefly looked into Terraform but decides to stick with Cloudformation because our task was relatively "simple". Apparently if it's a bit more complex, Terraform might be the way to go.

Incentivized

• Positive - Inter-department report flow was quick.
• Positive - Defined process gave us a defined to finish our goals.
• Negative - Detailing on each module is less.

Incentivized

• It has a positive ROI
• Less time inverted in bugs
• More stable source code

Incentivized