Coded Apps - Data Fabric vs SQL Server vs Data Fabric + SQL sync?

Help Apps
1

Title: Coded Apps — Data Fabric vs SQL Server vs Data Fabric + SQL sync?

Hi everyone,

We’re currently exploring UiPath Coded Apps for a new solution and are looking at different options for the backend/data storage. Nothing has been decided yet, so I wanted to get some thoughts from people who have worked with these approaches.

So far, we’re considering:

Option 1 - Data Fabric only
Coded App → Data Fabric

Option 2 - SQL Server as the backend
Coded App → secured REST API → SQL Server

Option 3 - SQL Server + Data Fabric synchronization
Coded App → Data Fabric ↔ UiPath Process ↔ SQL Server

For Option 3, the idea would be to have the data stored in SQL Server and use a UiPath process to synchronize the relevant data between SQL and Data Fabric so the Coded App can work with the Data Fabric entities.

I’m mainly looking to get some thoughts on the pros/cons of these approaches and what others have seen work well.

For example:

  • Has anyone used a Coded App with SQL Server through a REST API?
  • Is the SQL + API approach practical and secure for a production application?
  • Has anyone used a SQL ↔ Data Fabric synchronization approach? How did that work out?
  • Does the synchronization approach add too much maintenance/complexity, or are there good reasons to have both?
  • If you’re starting a new Coded App solution, what would make you choose Data Fabric vs SQL vs a combination of both?

Just looking for ideas and experiences from anyone who’s worked with these architectures.

Thanks!

2

Hi @Kirbymisa, it is good start exploring coded apps the way you are doing.
Coming to your query for using SQL server with APIs, this would works as expected while you are developing and testing on your system. But you won’t be able to productionize it. The SQL server needs to get connected to Data Fabric via Integration Services.
I would rather choose working with data fabric to have better control and smooth integration.