Question about the project status

[WernerBuchert]

Hi.

Actually, I only have one question, hope that's okay.

Find Riak very interesting, just wondering what the state of riak is. There is still the basho/riak-core repository and then also riak.info, where you can download a current riak version in the download section in the kv directory.

riak.info

So I am a bit confused what is the relation of these three versions?
Are improvements in one of the branches taken over in others?

Which version is recommended or future-proof?

Thanks for your work and best regards,
Werner Buchert.

[albsch]

Hi!

So I am a bit confused what is the relation of these three versions?

As far as I know, there are currently two maintained versions of riak_core, the original riak_core and a simplified version, riak_core_lite.

riak.info lets you download the database riak kv, which is built using riak_core (not riak_core_lite).

Are improvements in one of the branches taken over in others?

Yes and no. Bug fixes and improvements are incorporated, if there are any. Feature extensions are first discussed (e.g. Rack awareness support). If there is no significant interest or if the complexity added is too much, new features won't be included.

Which version is recommended or future-proof?

It depends. If you want to use only the core features of riak_core and want to use up to date Erlang versions, you can start with riak_core_lite. Switching to riak_core is always possible without much hassle (for now), though not recommended. Switching from riak_core to riak_core_lite is not as easy if you rely on additional features.

I'll extend the Readme with more information on this topic when I have some free time.

The main goal of the riak_core_lite project is to provide a stable, tested (hopefully partially verified in the future) and easy-to-update (i.e. keeping up with new Erlang versions) code base.

[WernerBuchert]

Thank you for the detailed explanation.

[albsch]

I'll close this issue for now. If there's more questions, feel free to open a new issue or ask here, I'll reopen it.