Item: OutSystems
Rating: 4
Author: Verified User

Overall Satisfaction with OutSystems

Use Cases and Deployment Scope

OutSystems is used in creating a next-generation energy market SaaS solution. It is used in two development teams.

Pros and Cons

Pros

Learning curve for actual process implementation is remarkably low.
Integration to other systems is smooth ( e.g. developing a UI that uses Tableau works really well).
It's particularly easy to extend OutSystems with your own .Net solutions.

Cons

Licensing model does not allow an easy way to scale or rebuild your software stack in a public cloud environment.
OutSystems' scalability model leaves a question on how OutSystems behaves under a heavily varying workload.
OutSystems version control lacks support of branches, version comments, and version difference reviewing.

Return on Investment

Fast modeling and implementation time
Difficult automation and scaling
Needs cloud-specific components in front of and between platform services

Alternatives Considered

AWS Elastic Beanstalk, AWS Lambda and Docker

On AWS cloud all the examples work better from the platform point of view than OutSystems.

Other Software Used

Vertica, AWS Lambda, MySQL

Likelihood to Recommend

OutSystems fits well if the solution is hosted by OutSystems' own cloud platform or then hosted on-premises. Currently, it does not fit into a public cloud where you'd run it by yourself.

Comments

Please log in to join the conversation

A little hard to grasp for a DevOps pro