Cross-Compile Riak for Embedded Device

Stephen Etheridge setheridge at basho.com
Tue Feb 14 06:35:34 EST 2017


Darshan,

Magnus has stolen my thunder and words!  I agree that your use case, as
outlined by Magnus above, is not one Riak is aimed at.  In fact, given you
want to persist data on an embedded device, are you sure you even want the
overhead of a "database"?  There are the options Magnus mentioned above,
also you may want to look at:

http://www.yaffs.net/fuel-embedded-database-use-yaffs
http://www.mcobject.com/emb

I have not used either, but they may give you ideas.

In my embedded/IoT work I have not used the embedded device as a persistent
store, I have buffered readings on the edge devices but I have then, when a
connection is made, sent them to processing hubs.

Kind regards
Stephen

On 14 February 2017 at 10:45, Magnus Kessler <mkessler at basho.com> wrote:

> On 13 February 2017 at 16:06, Darshan Shah <dg.shah1991 at gmail.com> wrote:
>
>> Our main usecase is to create a database in Embedded system to store
>> value received from one server.
>> For our usecase Key value based database is best suitable and we found
>> Riak is one of best for this.
>> So we want to cross compile Riak databse for Embedded system.
>>
>> On Fri, Feb 10, 2017, 3:46 PM Stephen Etheridge <setheridge at basho.com>
>> wrote:
>>
>>> Darshan,
>>>
>>> Perhaps if you gave some more details of what you are trying to do I
>>> might be able to help further?
>>>
>>> Stephen
>>>
>>>
>>>
> Hi Darshan,
>
> If I understand you correctly, your embedded devices will locally store
> data and will communicate with a central server, but not other peer
> devices. Riak's strength lies in being a centralised distributed database
> optimised for dealing with very large data sets. Riak installations
> typically distribute the data set over a small(-ish) number of nodes to
> achieve high availability and resilience.
>
> In your use case I expect there to be a large number of embedded devices,
> each responsible for a small amount of data. This is not a good fit for
> Riak.
>
> A quick search shows embeddable key-value stores, such as RocksDB [0],
> unqlite [1], and others (*), which you could use to store data locally in
> your embedded devices. If you'd like to use Riak on the central server, I'd
> recommend using one of the Riak client libraries [2] to transfer data
> between the central server and your devices.
>
> Kind Regards,
>
> Magnus
>
> (*) The quoted embeddable DBs are examples only. I haven't personally used
> them yet, and can't vouch for their suitability for your project.
>
> [0]: http://rocksdb.org
> [1]: http://unqlite.org
> [2]: https://docs.basho.com/riak/kv/2.2.0/developing/client-libraries/
>
> --
> Magnus Kessler
> Client Services Engineer
> Basho Technologies Limited
>
> Registered Office - 8 Lincoln’s Inn Fields London WC2A 3BP Reg 07970431
>



-- 
{ "name" : "Stephen Etheridge",
   "title" : "Solution Architect, EMEA",
   "Organisation" : "Basho Technologies, Inc",
   "Telephone" : "07814 406662",
   "email" : "mailto:setheridge at basho.com",
   "github" : "http://github.com/datalemming",
   "twitter" : "@datalemming"}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20170214/7f6fb87d/attachment-0002.html>


More information about the riak-users mailing list