Skip to content

Comment on Consul, a new tool for service discovery and configurationparent

Comments

Consul is a totally different thing to Cassandra. Consul could be built on top of Cassandra, but it would not provide any advantages. Why would you want to maintain a separate datastore?

Consul is a single static binary that uses around 11MB of RAM. Cassandra is a complex distributed datastore that requires the JVM and uses many gigabytes of RAM.

Why would you want to maintain a separate service discovery cluster?

Cassandra is not a service discovery cluster...

I think you're missing the point here. I don't know what else can be explained better.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.