# TransportClient vs Cluster Client **URL:** \ **Category:** Elasticsearch\ **Created:** [August 30, 2012, 2:19pm UTC](https://discuss.elastic.co/t/transportclient-vs-cluster-client/8897 "2012-08-30T14:19:48Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Vinicius\_Carvalho](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinicius_carvalho/32/770_2.png) [@Vinicius\_Carvalho](https://discuss.elastic.co/u/Vinicius_Carvalho)\ **Post date:** [August 30, 2012, 2:19pm UTC](https://discuss.elastic.co/t/transportclient-vs-cluster-client/8897/1 "2012-08-30T14:19:48Z")
Hello there! I usually have my clients configured as transport only (testing), but now, moving into production I like the fact that cluster clients do not require a host address configuration. My production deployment will look something like this: 3 data nodes with 0 shards and 2 replication factor (the index is really small, we are actually using ES as our TokenRepository for auth) And around 70 clients executing GET operations on those nodes. I just would like to know if having 70 client nodes in the cluster could cause any networking issue, or unnecessary overhead on the servers. Regards -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:14am UTC](https://discuss.elastic.co/t/transportclient-vs-cluster-client/8897/2 "2017-07-06T03:14:33Z")
Closed on July 6, 2017, 3:14am UTC