Discussion:
[redis-db] Add zookeeper api to redis
iamybj via Redis DB
2018-11-17 03:39:28 UTC
Permalink
I recommend add zookeeper api to redis.
zookeeper api is very simple, people do not need to learn and maintains 2
technologies and servers.
also redis api is very ugly, it should be improved.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+***@googlegroups.com.
To post to this group, send email to redis-***@googlegroups.com.
Visit this group at https://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.
h***@gmail.com
2018-11-17 10:56:46 UTC
Permalink
Zookeeper is a quite specialized key/value store, with data and metadata
elements that work very differently from Redis. Znodes (equivalent to
Redis's keys) are small and Zookeeper enforces a size limit that's
typically 1 megabyte. They are also hierarchical, much like a
folder/subfolder tree in a filesystem. Zookeeper servers are a group of
writable peers that replicate to each other rather than Redis's
master/replica structure.

Trying to implement the Zookeeper API on top of a storage/replication
engine that behaves in such entirely different ways (like Redis) would be
more disappointing than it would be fulfilling. A significant amount of
the API would have to be omitted because the functionality isn't present in
Redis, and other parts would have behavior that differs from Zookeeper.
Some parts would have small differences, other parts large differences. As
I see it, it's like dressing up to go to a costume party. I can wear a
surgical scrubs, a lab coat, stethoscope, and surgical mask, but that
doesn't make me a medical doctor.

A carpenter's toolbox contains different tools that must be used
differently. Not all tools are for striking things like a hammer, and
there are even different hammers in the toolbox because a carpenter needs
more than one way to strike a nail or piece of wood. In the same way there
are many different software daemons for storing and retrieving data - SQL
stores, document stores, key/value stores - and each is a tool that works
in a different way. Even among key/value stores there are different
daemons that solve different problems and work differently from each
other. Their APIs reflect the work that can be accomplished through the
back-end engine. The differences are not something that can be avoided.
Pick the fewest data stores that will accomplish the work that you need to
perform, and you will only have to learn those few APIs.
Post by iamybj via Redis DB
I recommend add zookeeper api to redis.
zookeeper api is very simple, people do not need to learn and maintains 2
technologies and servers.
also redis api is very ugly, it should be improved.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+***@googlegroups.com.
To post to this group, send email to redis-***@googlegroups.com.
Visit this group at https://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.
Geoffrey Hoffman
2018-11-17 14:50:43 UTC
Permalink
Post by iamybj via Redis DB
redis api is very ugly, it should be improved
I don’t think a lot of folks on here will take you seriously with a statement like that.

Kids in their parents basement, youtubers, small to Fortune 500 companies have managed to grow thousand/million/billion dollar businesses on it - can’t be that bad.

Try any one of the dozens if not hundreds of clients already written. Almost no one deals directly with raw Redis communication from their application. If you are, you might be using lolcode.

Send us a link to your “pretty” API then.

For me, Redis is sexy as hell.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+***@googlegroups.com.
To post to this group, send email to redis-***@googlegroups.com.
Visit this group at https://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.
Salvatore Sanfilippo
2018-11-19 11:59:04 UTC
Permalink
Post by iamybj via Redis DB
also redis api is very ugly, it should be improved.
Hi, sometimes people refer to the Redis API as of "assembly for
databases". This may look strange if you come from different
technologies or just don't like such design, but Redis was designed
specifically in this way, with commands that as a side effect modify
data structures (or read them).
There are many many different potential APIs. I chosen this one 10
years ago and we managed to survive a decade :-) So I think we'll go
forward with such API. Thanks for the feedback.
On Sat, Nov 17, 2018 at 9:31 AM iamybj via Redis DB
Post by iamybj via Redis DB
I recommend add zookeeper api to redis.
zookeeper api is very simple, people do not need to learn and maintains 2 technologies and servers.
also redis api is very ugly, it should be improved.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
Visit this group at https://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.
--
Salvatore 'antirez' Sanfilippo
open source developer - Redis Labs https://redislabs.com

"If a system is to have conceptual integrity, someone must control the
concepts."
— Fred Brooks, "The Mythical Man-Month", 1975.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+***@googlegroups.com.
To post to this group, send email to redis-***@googlegroups.com.
Visit this group at https://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.
Loading...