OutSystems Hub Edition 3.0 Sneak Preview

OutSystems Hub Edition 3.0 Sneak Preview

Hello all,

I'm glad to announce and provide you with some insights about the fore coming OutSystems Hub Edition 3.0. With this version, OutSystems speeds up pace towards a fully modular and portable enterprise application architecture, aligned with existing popular and simplified "Built-to-Change Enterprise Application" approach.

Second generation eSpaces

OutSystems Hub Edition 3.0 introduces eSpace References, which allow you to easily share Actions, Entities and Structures between eSpaces. Now, you can easily mark your eSpace objects as public. References to those objects can be added to other eSpaces within your Hub Server installation allowing you to architect your applications in multiple eSpaces, adding references among them, increasing modularity and reusability. .

Also, you can group your application business rules in a separate eSpaces by defining a sets of Entities and their related Actions and Structures. Thereafter, new applications may be built just by composing these public Actions and Entities into new Screens that integrate functionality from each module! For those of you acquainted with External Entities, it has a similar concept with a similar behavior, now adding Actions and Structures, plus a dedicated tool (see screenshot) in Service Studio.

Collaborate in extreme change conditions

Taking a first look into eSpace References, you may consider that although it is a very interesting and compelling new feature, it introduces a management and maintenance overhead to track several eSpaces for each application, instead of just one. Actually, we've introduced change automation and tracking tools that remove the application maintenance overhead and assist you during the development of your applications. This way, OutSystems enhances and keeps the edge as a leading "Built-to-Change Enterprise Applications" platform.

How does it work? It is fully integrated with the 1-Click Publishing process. When publishing a new version of an eSpace you'll be notified about changes in the eSpaces you're referencing. If these changes don't affect the programming interfaces you're using, your eSpace will run along with the most recent version of the eSpace you're referencing without any changes. If they affect the programming interface you'll immediately obtain verify warnings or errors that you can immediately correct as you now do when you change an Action inside your eSpace.

Select the database server of your preference

With OutSystems Hub Edition 3.0 you may install the OutSystems Hub Server on top of a Microsoft SQL Server or an Oracle database management system. This means that, from now on, the same application, designed with OutSystems Service Studio, can be deployed in the database server of your choice!

If you're thinking about using the OutSystems Hub Edition with Oracle, notice that all your eSpaces can be immediately published with the new Hub Server version. You'll just need to check your Advanced Queries (with the help of Service Studio) for any specific Microsoft SQL Server SQL syntax usage.

Next Steps

OutSystems Hub Edition 3.0 is planned to be released at the end of October. Until then you'll receive additional and more detailed information about "What's New" in this release. There are also a lot of minor changes that will also please you! We'll let you know.
I hope you can find this information useful. Don't hesitate to post your comments or doubts.

Thank you,

Carlos Alves

This is looking very good!
Will we be able to use the MySQL database server? What about PostgreSQL?



OutSystems Hub Edition 3.0 will only include support for Microsoft SQL Server and Oracle.

We decided to support these leading RDBMS based on market information and feedback from our customers and partners.

Anyway, your feedback is valuable for future versions.

I wonder if any of you have similar requirements. Please let me know.

Thank you,

Carlos Alves

There are a few reasons why it would be nice to have OutSystems run on MySQL:

- transactionless query'ing is very well implemented in MySQL, and especially MyISAM tables are very very fast; very-big-and-busy-table problems you could have with MS SQL can be easily solved on a database level using MySQL and INSERT DELAYED

- we don't really need transactions for 99% of our business logic, and if we need it, we could make our tables to be of InnoDB types

- MySQL is open source and free, so any database problems we could be having can be solved ourselves, or by the open source community, without the need of waiting for another payed upgrade

Most of the advantages stated above also apply to PostgreSQL.


Hi Jurriaan,

Regarding your pros for MySQL:

- It is possible to use SQL Server without transactions (the feature is called autocommit). Would you consider using SQL Server in this mode? If so, maybe we can support it in OHE in the near future as an alternative to fully support another database server.

- About technical support for open source products against technical support for commercial products, I think that would be a long discussion :) in this scope... I leave it up to you.

Thank you again,

Carlos Alves