# Kibana version 4 architecture **URL:** \ **Category:** Elasticsearch\ **Created:** [January 5, 2015, 3:29pm UTC](https://discuss.elastic.co/t/kibana-version-4-architecture/21485 "2015-01-05T15:29:55Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![bitsofinfo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bitsofinfo/32/459_2.png) [@bitsofinfo](https://discuss.elastic.co/u/bitsofinfo)\ **Post date:** [January 5, 2015, 3:29pm UTC](https://discuss.elastic.co/t/kibana-version-4-architecture/21485/1 "2015-01-05T15:29:55Z")
Hi Starting to experiment w/ Kibana 4. I see that now there is a server side component where it appears all client requests proxy through? What is the recommended topology for deploying this for HA,\* is there any client session state maintained in this server side process or is it pretty much a stateless proxy\*? What does the server side component actually do now, that was offloaded from the prior kibana architecture where everything was only in the UI? thanks! -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/634084f9-c04d-488e-baa7-c1f692c06d8e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/634084f9-c04d-488e-baa7-c1f692c06d8e%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:40am UTC](https://discuss.elastic.co/t/kibana-version-4-architecture/21485/2 "2017-07-06T00:40:49Z")