Outsystems Architecture and Governance

Outsystems Architecture and Governance

  

Hello Experts, 

I am a newbie to Outsystems. Looking at Out systems from a Enterprise Architecture perspective, doesnt anyone has a built or comeacross a 

- Reference Architecture for Outsystems platform

- Application reference Architecture 

- Governance model to promote re-usability ?

- DevOps process model ?

Thanks in advance..

Hi,


Did you check https://www.outsystems.com/learn/Learn.aspx ?

and for example:

- https://www.outsystems.com/learn/paths/9/devops-in-outsystems/

- https://www.outsystems.com/learn/paths/8/architecting-sustainable-applications/

- https://www.outsystems.com/learn/paths/17/becoming-a-tech-lead/


Is there a reason why you could not find it?

Because it's very easy to find, so I am curious why you were not able to find it.

J. wrote:

Hi,


Did you check https://www.outsystems.com/learn/Learn.aspx ?

and for example:

- https://www.outsystems.com/learn/paths/9/devops-in-outsystems/

- https://www.outsystems.com/learn/paths/8/architecting-sustainable-applications/

- https://www.outsystems.com/learn/paths/17/becoming-a-tech-lead/


Is there a reason why you could not find it?

Because it's very easy to find, so I am curious why you were not able to find it.

Hello J,


Yeah, i had a look at the guided paths, however most of the paths focus has been on building an application.When the adoption of Outsystems increases across the organization, tand at the same time tech savvy business Analysts start building their own apps. When this happens 

- The number of apps that are being built grow very quickly 

- Every division/teams does their own, There will be a lot of apps and very less re-usability. Avoid 

- Tech-savvy business Analysts can build their own apps with no reference Architecture to follow and it  becomes very difficult for support teams for application administration.


As an Architect, i see  the success of Outsystems from a strategic perspective will really depends on how  governance is enforced through processes , Architecture standards, reference Architecture.. 



Well,


Doesn't it integrate with the company-architecture?

How do you want the integrations, authentications etc.

So I think you will have to create your own enterprise vision on how it should be.

and try to tackle specific issues that you might have a challenge with.


There are some really good slides on the 4-layer architecture, so I am surpised you did not spot them.

perhaps you can look at the playbooks to get even more information:

https://www.outsystems.com/resources/

 


Raghavendra Kummari wrote:

tech savvy business Analysts start building their own apps. When this happens 

- The number of apps that are being built grow very quickly 

- Every division/teams does their own, There will be a lot of apps and very less re-usability. Avoid 

- Tech-savvy business Analysts can build their own apps with no reference Architecture to follow and it  becomes very difficult for support teams for application administration.

Hi Raghavendra,

Only those that have explicitly been given the right privileges can develop apps in a certain environment. Everybody can develop their own apps in their Personal Environment, but these can't be transfered to the corporate environment. In LifeTime, part of the OutSystems Platform, you can configure who has a role of Software Developer, and so who can develop at all. If you are not registered as developer, you cannot log on to an environment, and hence not "start building [your] own apps".

As for reusability, that's not a question of a specific Platform. With any software platform, low code or not, co-operation and reusability is a matter of company processes and agreements, not of that platform.

I think all your other questions can be answered by taking a look at the documentation that J supplied.


J. wrote:

Well,


Doesn't it integrate with the company-architecture?

How do you want the integrations, authentications etc.

So I think you will have to create your own enterprise vision on how it should be.

and try to tackle specific issues that you might have a challenge with.


There are some really good slides on the 4-layer architecture, so I am surpised you did not spot them.

perhaps you can look at the playbooks to get even more information:

https://www.outsystems.com/resources/

 


thanks for the feedback J and Kilian.