In the next development wave, codename Io.Ga.Co some features necessary in the IoT realm will be implemented. Even if you are not interested in IoT development, some of the implemented features will be useful for traditional enterprise IT as well.
FLoM project supplies a set of useful synchronization tools: it can be used from a command line, from a shell script or from a real application using one of the supplied client binding libraries.
IoT planet needs to deploy a huge number of gateways to adapt the impedance between the devices and enterprise IT.
Every land populated by distributed computing needs some form of synchronization to implement some use cases: the Io.Ga.Co evolution proposes to use an enhanced version of FLoM as a component to deploy inside IoT Gateways.
These are the features proposed for the next implementation wave.
Security is the main concern of IoT applications: introducing authentication and cryptography is a necessary step to operate in the wild.
IoT needs IPv6 to connect billions of devices, this is a must have feature to deploy FLoM in the IoT realm.
Sequences are widely used to generate unique consecutive ids: no one would use a relational database just to manage a bunch of sequences.
Implementing a synchronized resource that behaves like a distributed sequence that can be accessed from everywhere by the authorized clients is a natural evolution step for FLoM.
Like sequences, some use cases need unique timestamps with a desired granularity (seconds, milliseconds, etc...).
Implementing a synchronized resource that behaves like a unique timestamp generator that can be accessed from everywhere by the authorized clients is a natural evolution step for FLoM.
Becoming a Docker enabled component can be very practical for cloud deployment of the future FLoM IoT Gateway Component.
If FLoM supported mission critical use cases, it should supply some form of high availability in case of hardware or software failure.
Some use cases, like distributed sequences need resources that survive system restarts.
Long term persistence is not disjoined from Native high availability feature.
Currently FLoM uses XML to serialize and deserialize the data that must be transmitted; IoT tends to use binary technologies to save electric power. The venerable ASN.1 might be a very consolidated and efficient choice; an alternative approach could be the usage of Apache Thrift.
Use this Doodle to select the most important features from your point of view.
Use the General Discussion Forum to report your feedback.