If you were talking to someone whose organization is considering OutSystems, what would you say?
How would you rate it and why? Any other tips or advice?
I will rate OutSystems a nine out of ten because if you look at other solutions, they do not have the functionality, the scalability and the performance of OutSystems, even if their prices are lower. So if you need a platform for a large organization, OutSystems is the one. To make it the perfect solution, it needs improvement in the AI capability. I would say that it would be nice to augment the functionality for the citizen development even further and augment the cloud's platform controls so that you can more easily run in a hybrid cloud environment too. Next to better branching options. A word of advice to others is that they should align the business and IT because many people look at it from a technical point of view. And that is another really smart thing to do because it is really about driving the value. Because I've seen customers that bought either mandates or OutSystems or any other platforms and a lot of them had difficulties in getting the value out of it. And the reason was because if the IT or individual departments don't know how to define the proper user requirements, and then it is too difficult to successfully deploy it. It is therefore very important for the business and IT team to work together because that is the most common mistake people make.
We find in OutSystems a great platform that enables extraction of data from multiple sources, and working with business logic to access essential information and produce process-automation at the highest level. We have future projects in mind to build factory production process with this technology. New developers were recently hired to support the industrial development team and they are being progressively coached in OutSystems development, using an internal training program to reach this goal. We rate OutSystems an eight out of 10. It is the best platform we have found. However, it’s not perfect. In terms of advice: * When possible, use a cloud environment option rather than a local installation. * Negotiate a suitable license with OutSystems, taking into account that the application objects grow quickly. * Hire trainers and make sure the development team sets up a proper architecture. If you choose the wrong approach or do not plan appropriate architecture, in a short time you will certainly have a very large rework. * It is essential to build an appropriate Canvas. * Sometimes, junior developers will perform better with OutSystems, since senior developers often do not adapt to the graphical structural programming. It is not a rule, but some resistance and difficulty of adaptation were noticed. * A good practice is to hire an expert consulting company, for a couple weeks, which already uses OutSystems. They will help your development team with basic questions, increasing the pace of learning and making it more effective. * OutSystems has a set of metadata and any kind of control is possible, but these structures should be practiced with the developers. * OutSystems Forge is a very useful place, when starting out, to download components to adapt to your needs. * SQL Server is a good default database option for OutSystems. We have never had a problem with it. We recommend using only a single database catalog instead of many. * Another suggestion is to plan an approach for the REST/SOAP APIs with more security implementations. As a default, it provides NTLM authentication or basic authentication to SOAP API and a custom strategy for REST. We have built a complete architecture with client authorization, IP control, and cryptography over the exposed services. The OutSystems User Provider module can be customized with the company’s default authentication method, however, it is quite simple to maintain the standard module and just push data into the Users and Roles tables. Otherwise, it will take some time to understand how everything works underneath. * Finally, perhaps the most important tip is regarding development governance. Not only for OutSystems but for all types of development, it is very important to maintain normalized and standardized environments. In a chaotic scene with no effort to have periodic reviews, a low-code platform could create a huge mess and the cost will be paid in the near future.
Agile development is really worth it. Depending on the size of your department – and requirements – you don’t need a big development team. The same developer can take care of all steps: analysis, development, implementation, support.
I rate it a 10 out of 10. It is fantastic how fast we can build an application. We have a lot of users and the community is growing.
The conventional coding rules don't apply here. You need to have an open mind and let the platform take control from you at times.
I started using this solution in 2012 and still am using it for many of our customers and internal projects. OutSystems is a robust, low-code platform that can make a big difference in your customer satisfaction. The overall features of the platform and continuous improvement make it more adaptable than other tools.