4 ms·

As someone who has spent the past year and change developing an automation system using the targeted platform (Megas) I can say that this sounds like a very bad

by Carrok 11y ago

As someone who has spent the past year and change developing an automation system using the targeted platform (Megas) I can say that this sounds like a very bad way to do things. While I applaud the effort, and it will certainly be useful for many people for many other reasons, I don't think IoT is the best use case here. If your data is at all valuable/useful, you don't want it sitting out somewhere on some device that will hopefully/maybe be online when you go to query it. Plus now just to be able to query it remotely you will still need to develop some sort of API that lives on the device that can talk to the LittleD database. Finally if you really are doing 'IoT' you clearly have a bunch of things that you want to view/control from a centralized platform. When you have the devices talking to a server, you can do this. When you have to ask each device individually what is going on with it, this becomes much harder.

geedy 11y ago
There isn't really a targeted platform. There just only happens to be one of me at the moment, and so I've only managed to compile it for a few devices. As you noted, its not really an IoT databases. It could be used as such, but thats not the reason I built it. I have also been working on the data transfer problem, because without the ability the share the data it is in fact kind of a useless platform in many applications. I have a job manager being developed that will allow for scheduled or ad-hoc execution of functions. I've also written some small library to encode LittleD results for network transmission. Using some basic networking stack, it would be easy to assemble these pieces into something that could be viewed/controlled from a centralized platform. LittleD could even be modified with relative ease to actually query over other LittleD instances! EDIT: I would actually like to encourage you to divulge some specific criticism for the IoT application. Are you specifically speaking to your automation system, or to IoT at large? It seems difficult to predict exactly how any one person might apply any given technology.
- jchrisa 11y ago
  We've built a sync-enabled database, and even at 500 kb it's getting a lot of uptake in IoT applications. Open source databases: http://developer.couchbase.com/mobile http://developer.couchbase.com/mobile Info about how GE is using it: http://www.couchbase.com/nosql-resources/presentations/offline-first-and-how-ge-integrated-couchbase-mobile-in-less-than-90-days.html http://www.couchbase.com/nosql-resources/presentations/offli... Long story short: when you get the network stuff figured out, it's gonna be an interesting product. Feel free to contact me (info in profile) if you want to chat about how this can fit into the industry.
  - jack12 11y ago
    When you say IoT applications, do you mean phone apps which are dealing with data which originated from a "thing" in the IoT, but that the data has already gotten to the phone or cloud through some other, non-Couchbase Mobile channel? Or is it possible to run or communicate/sync with Couchbase Mobile directly from a "thing" itself?
    - jchrisa 11y ago
      Couchbase Mobile has an optional on device rest API we use for p2p sync. You can also use it to push data from edge devices to a handset or base station, but typically phones will ping devices.
teraflop 11y ago
That seems like a narrow-minded and dismissive thing to say unless you know what the intended use case is. What if these IoT devices aren't just dumb sensors, and need to control some process? Then your argument is reversed; you want the data to be available locally, instead of having to contact a remote server that "will hopefully/maybe be online".
__jal 11y ago
I don't work with Megas, but I have to say this sounds like a terribly brittle view. Frequently it is exactly when connectivity is gone that you want some intelligence combined with data upon which to act, or a buffer in which to spool data. Otherwise you've just got a pile of sensors that are slightly easier to deploy than the ones with long extension cords. Put another way, > If your data is at all valuable/useful, you don't want it sitting out somewhere on some device that will hopefully/maybe be online when you go to query it. So what do you do with data on your device when it is offline? If it is at all valuable/useful, hopefully you're not just dropping it on the floor when Daddy-node is unreachable. Sounds like a job for which some sort of structured data store might be useful...

by Carrok 11y ago

geedy 11y ago

There isn't really a targeted platform. There just only happens to be one of me at the moment, and so I've only managed to compile it for a few devices. As you noted, its not really an IoT databases. It could be used as such, but thats not the reason I built it. I have also been working on the data transfer problem, because without the ability the share the data it is in fact kind of a useless platform in many applications. I have a job manager being developed that will allow for scheduled or ad-hoc execution of functions. I've also written some small library to encode LittleD results for network transmission. Using some basic networking stack, it would be easy to assemble these pieces into something that could be viewed/controlled from a centralized platform. LittleD could even be modified with relative ease to actually query over other LittleD instances! EDIT: I would actually like to encourage you to divulge some specific criticism for the IoT application. Are you specifically speaking to your automation system, or to IoT at large? It seems difficult to predict exactly how any one person might apply any given technology.

jchrisa 11y ago
We've built a sync-enabled database, and even at 500 kb it's getting a lot of uptake in IoT applications. Open source databases: http://developer.couchbase.com/mobile http://developer.couchbase.com/mobile Info about how GE is using it: http://www.couchbase.com/nosql-resources/presentations/offline-first-and-how-ge-integrated-couchbase-mobile-in-less-than-90-days.html http://www.couchbase.com/nosql-resources/presentations/offli... Long story short: when you get the network stuff figured out, it's gonna be an interesting product. Feel free to contact me (info in profile) if you want to chat about how this can fit into the industry.
- jack12 11y ago
  When you say IoT applications, do you mean phone apps which are dealing with data which originated from a "thing" in the IoT, but that the data has already gotten to the phone or cloud through some other, non-Couchbase Mobile channel? Or is it possible to run or communicate/sync with Couchbase Mobile directly from a "thing" itself?
  - jchrisa 11y ago
    Couchbase Mobile has an optional on device rest API we use for p2p sync. You can also use it to push data from edge devices to a handset or base station, but typically phones will ping devices.

teraflop 11y ago

That seems like a narrow-minded and dismissive thing to say unless you know what the intended use case is. What if these IoT devices aren't just dumb sensors, and need to control some process? Then your argument is reversed; you want the data to be available locally, instead of having to contact a remote server that "will hopefully/maybe be online".

__jal 11y ago

I don't work with Megas, but I have to say this sounds like a terribly brittle view. Frequently it is exactly when connectivity is gone that you want some intelligence combined with data upon which to act, or a buffer in which to spool data. Otherwise you've just got a pile of sensors that are slightly easier to deploy than the ones with long extension cords. Put another way, > If your data is at all valuable/useful, you don't want it sitting out somewhere on some device that will hopefully/maybe be online when you go to query it. So what do you do with data on your device when it is offline? If it is at all valuable/useful, hopefully you're not just dropping it on the floor when Daddy-node is unreachable. Sounds like a job for which some sort of structured data store might be useful...