Yeah, Cassandra uses a Distributed Hash Table with Consistent Hashing.
When a new node added, it takes responsibility for a segment of a ring. When node removed, it's segment get redistributed.
It's however in no way a drop-in replacement for RDBMS and requires a careful planning around application read and writes patterns that is very different from your typical RDBMS. Definitely, can't be used in this scenario - every node needs to be able to access every other node and client must be able to access at least one node.
I believe Cassandra does not have a Master\follower architecture; it's following a ring based structure.