Overview – Building A Foldda Solution

Foldda solution is built using Windows folders, thus the process is primarily cut-n-paste, drag-n-drop, etc.

As we show you in the Quick-start Guide, a Foldda solution is a data-processing program that can consist of one or many data-processing pipelines called data-flows. Logically a data-flow is sequential of data-processing steps that each implements a part of the overall solution.

Physically a Foldda solution is made with a collection of related special (file-system) folders. When running a Foldda solution, you would start by loading the solution into its execution environment called a Solution Runtime, so in loading a solution, you would refer to the runtime where the solution resides – which is a file-system directory (i.e. a folder) called a Solution Home Folder.  

Within the Solution Home folder, it contains a hierarchy of sub-folders called Folder nodes. Each node folder contains the implementation of a specific solution data-processing step – a program module called a Handler

Foldda Integrator cleverly uses a computer’s file system’s folder-hierarchy to represent a data-process flow’s sequential steps, so it avoids the need for an IDE for building a data-processing program. Because building a Foldda solution is literally copy-n-paste folders and stacking node folders into a hierarchical tree structure that represents a data-flow, these operations can be performed anywhere on any computer without having to install extra software tools, and they are familiar to every computer user.

Let’s illustrate building a Foldda solution using a mock-up example:

Step 1: Design a logical data-flow

Usually, a data-processing project would start by defining the requirement. You may sketch the processing’s logical data-flow on a piece of paper, like this – 

Step 2: Choosing suitable handlers

The Foldda Integrator download contains a sub-folder called “handlers-inventory”, it contains pre-built Foldda folders each is configured with a supported handler – 

For our example, these are the Foldda handlers we choose to use –

Step 3: Building the data-flow

Based on the data processing’s sequential order, stack the selected handler folders into a nested parent-child relationship, like this –

Done, we have just completed building the solution’s data-flow. We will still need to set the handlers’ parameters to suit our requirements, and this post shows you how to change Foldda node settings.

Demo and Summary

The following animation shows how the above steps are done – it shows you can build a solution literally in seconds.

As you see, building Foldda solution is just stacking handler folders in the order required by the data-processing, Because there is no need for using an IDE, you can build Foldda solution anywhere on any computer, and the developed solutions can be easily deployed, and be managed – they are just folders, you can easily make backup copies of your solution, make different versions, share the solution with your colleagues, or distribute it to your clients. 

Now you have seen how to build a Foldda solution in this example, you can explore and mix-n-match the handlers to build the solution for your own requirement. Because Foldda Integrator is a portable program, you can run your solution from a USB on any PC. You can also run your solution as Windows service on a server, so it can process data according to your requirement 24×7.