We will create a small web application as a first project in OutSystems to gather knowledge about the tool. We have access to API's through Amazon API Gateway. However all the data we require is not in our RDS environment, but rather manually entered based on a static list. We do however ultimately need this data in RDS.
Should we use RDS as our main entity and cache our results or simply use local entities and synchronise them every so often?
Hi,
OutSystems has its own database (MS SQL Server by default, but you can request Oracle) running in the infrastructure they host for you as RDS.
If you need to connect to your own RDS you can setup a database connection.
But to make an app and store the registered data in a database, you don't need anything else just OutSystems, and there is a lot of benefits to do this in OutSystems, foremost you already pay for the database in your outsystems license, so why pay for another RDS subscription. Second using the OutSystems database, you have all the benefits of OutSystems automating the complete process of creating and maintaining your database schema, so you don't require a skilled database administrator.
Regards,
Daniel
We need RDS regardless of OutSystems or not, there's data being gathered for applications to run on.
Would you advise using the OutSystems database and setting up a synchronisation or using the API with cached results? This specific data is irrelevant to the operation of other things.
The choice between using RDS as the primary entity or local entities with periodic synchronization depends on your specific requirements, and both options are feasible.
Accessing the OutSystems database can present challenges, and guidelines for this can be found at https://success.outsystems.com/support/enterprise_customers/maintenance_and_operations/access_the_database_of_your_outsystems_cloud/.
Our primary method for approaching this is to make outsystems entities and interact through the exposure of RESTful APIs.