Another way to provide data via web-apps (an MDS alternative)
Tags: mds, stadium6, lowcode, frontend
Published: 2022-08-01 09:12:24

Making data available via a front-end can be a headache when your _(back-end)_ team is busy with other high-priority tasks. It can be an even greater challenge when there are requests to update specific records or to allow specific users to have access to change very specific fields. MDS is always an option, but it has some limitations and availability constraints. 

Let's say we need to make data available for our users. Some users need to be able to simply view it, and others need access to update certain fields. What if our users also want some bespoke functionality that we need to add in such as validations, business rules or simply notifications that fields were updated? 

This bespoke functionality can go beyond just data, for example, what if our user needs to upload a file that needs to be loaded via a back-end process? 

## MDS Alternatives 

MDS or similar alternatives will not easily suit our needs with regard to the above-mentioned scenario. We can opt to create a bespoke single-page application (SPA) via a popular web framework, but this can be costly, time intensive and come with a high skill requirement. 

Another option is to turn to a low-code alternative, like [Stadium](https://stadium.software/stadium-6-is-live/), to speed up our development. There are many other options available, but I found that Stadium offers the tools that I need to make data available, add bespoke functionality and do it all with little front-end development knowledge. 


![A gif that shows how low-code can be used to create an MDM like site](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/uuic2r6beyyj4ro7873x.gif)

## Make data available fast

The goal of any MDM-like tool is to make data available for users to interact with quickly. With [Stadium](https://stadium.software/), I was able to do so in a few clicks. I could also make a simple editor by combining SQL scripts (generated by Stadium with some amendments) for a row of data. This highlights that it is possible to create dynamic and rich user experiences with Stadium. The below gif illustrates what I was able to do in a few clicks: 

![A gif that shows ](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/4ujbuggxepyf04oct5bv.gif)

## More than just data availability

A big trap that I have personally fallen into is to force a tool like MDS to do things that it is not made for, such as kick-off processes. I am a big fan of the ‘tool for every job’ mentality. Using the right tool to create a bespoke screen that can upload files, kick off processes or act as a data dashboard is very important, but finding the right tool that can integrate all these tasks can be a challenge. 

This is where I feel that Stadium does a good job. It allows you to create web applications without restricting you to a specific path. You can create a simple application that will replace or enhance your MDS functionality, you can create dashboards, create pages that will assist users with business processes or create a file management system where users can upload and maintain files to be loaded into the database via your back-end processes. Stadium also works great with any back-end, but I highly recommend trying [Linx](https://linx.software/) with Stadium.

## Conclusion
Making data available to your users via a front-end can be a bit of a headache when you do not have the tools or skillset to do so. [Stadium](https://stadium.software/) and tools like it can speed up front-end development, helping with those tight deadlines. Just be sure that the low-code tool you select is correct for what you are trying to accomplish.  

![A gif showing how Stadium works and how it can be used to create an MDS like front-end](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/g548iyskxmmyp10svn73.gif)

Read more on the latest Stadium release [here](https://stadium.software/stadium-6-is-live-%f0%9f%9a%80/).