Comments (8)
All the server needs to store is messages being transferred between clients (sources and sinks). Considering between RDMS Postgres | MongoDB | Redis.
http://slashdot.org/topic/bi/sql-vs-nosql-which-is-better/
http://redis.io/
From preliminary research, looks like non-SQL is better since since they store data as native JS objects or JSON.
Options:
MongoDB
Redis
Couch
Riak
from iolibrary.
MongoDB seems to be a better option to deal with large datasets. MongoDB it is then.
from iolibrary.
to enable database recording:
node app.js 9090 / true
from iolibrary.
A better way needed to organise between runs. i.e so users can view results from previous runs as well. Not just the current one.
from iolibrary.
from iolibrary.
From the portal, only one instance of a workflow can be executed at one time. But the portal does not keep track of the runs. I need to store information about runs if want to access the history.
From the portal, it needs to record:
- run id
- workflow id
- start run
- end run
- maybe provenance database
In the server, it needs to record:
- actor definition - so that the history portlet can get the appropriate objects to display data
- run id, and time
- workflow id
- messages exchanged between IOActors, IOPortlets. The history porlet will just display messages from IOActors.
In the portlet, it needs to record:
- history of the messages
Now the question is whether the database should be centralised ?
from iolibrary.
Note that enabling viewing history of the current run is easy. But viewing history of previous runs are harder. Keep in mind for the future extension.
from iolibrary.
Possible Solution:
- in each workflow, three parameters are required: "username", "password" and "runid". username and password are string parameters
- when the workflow is executed, these two parameters are passed to workflow
- IOActor will look for these two parametrs in the top level container, if not --> throw exception
- add these two parameters in the definition
Changes needed:
- WorkflowsList portlet
- Slavisa kepler client
- IOActor
- app.js to include run id, etc.
from iolibrary.
Related Issues (1)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from iolibrary.