Today’s BI tools are similar to reading an interactive news paper. Normally they’re read-only views looking at data about a day old (depending on when the transactional data was moved into the reporting warehouse), and they provide some slicing / dicing and drill down capabilities. Tableau and Qlik are probably the most widely used tools for this. Don’t get me wrong, interactive dashboards are cool and provide great eye-candy for PowerPoint decks …. but what business problems are they solving after deployment? The act of creating these dashboards is where the true insights are found. Normally, once created, data scientists have already discovered the interesting things with the data …
The biggest problem is your business isn’t read-only … people need to actually do things … manipulate data … and move the business forward. That’s where Composable fits in. Composable allows for all the operations in C.R.U.D. – Create, Read, Update, Delete …. not just Read. With Composable, you can actually build data models, and users can perform line-level updates.
Say, you need a database and a Web UI for viewing and manipulating data. You’re probably now asking, if you’re doing more complicated stuff than dynamic SQL queries and ETL, won’t you need a massive software engineering budget? After all, a software engineering team is going to need to develop:
- The Data Model
- ORM (Object Relational Mapper)
- SQL Queries for more complicated queries
- Web Services
- JSON Contracts
- Ajax calls
The answer: No. Composable can do all that for you. Here’s how:
Just define your model in Excel. Essentially each tab is a table.
Then upload it to Composable. We’ll generate the database, ORM layer, and produce a beautiful web UI for you to navigate. And we’ve got all the knobs for customizations.
Here’s we can see the database auto-generated for you. Composable lays out the tables perfectly – creating the primary and foreign keys, constraints, and categories.
An ORM is generated for you. Now you can reference and code directly against this if you need it. Internally, Composable uses this ORM to do most of the the data manipulation and querying.
And finally, you have a UI for navigating your entire data model. Note that the Url perserves the hierarchy of your data model.
Please check out Ryan’s post for more details on our Forms feature.
Latest posts by Lars Fiedler (see all)
- Migrating a FoxPro Database to 64 bit SQL Server - September 25, 2017
- Disabling MouseWheel Scroll Event on jQuery UI’s spinner control - June 21, 2017
- Search Features in Composable Forms - March 22, 2017