# Best practice for APM?

**URL:** https://discuss.elastic.co/t/best-practice-for-apm/195646
**Category:** APM
**Tags:** server
**Created:** [August 18, 2019, 12:11pm UTC](https://discuss.elastic.co/t/best-practice-for-apm/195646 "2019-08-18T12:11:38Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Eyal\_Koren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eyal_koren/32/36830_2.png) [@Eyal\_Koren](https://discuss.elastic.co/u/Eyal_Koren)
#### Post date: [August 18, 2019, 12:46pm UTC](https://discuss.elastic.co/t/best-practice-for-apm/195646/2 "2019-08-18T12:46:36Z")

</div>

Hi Eyal, what a beautiful name 🙂

You can look at the APM server as a scalable ingestion layer for data produced by APM agents into Elasticsearch, so certainly no need for a container per agent, unless very specific restrictions/limitations enforce that.

Regarding sizing, see [the relevant documentation](https://www.elastic.co/guide/en/apm/server/current/sizing-guide.html) and look for former discussions like [this one](https://discuss.elastic.co/t/apm-server-recommendations/145447).

However, the actual required size largely depends on each specific use case. I'd say the easiest way to onboard would be a cloud free trial. Just spin off a cluster with an APM server, start sending APM data into it, and see how your `apm-*` indices behave over time. Of course you can do the same with an installed APM server.

Since you are expecting mostly Javascript and Java, I would also suggest you follow through [this useful blog post](https://www.elastic.co/blog/performing-real-user-monitoring-rum-with-elastic-apm) that includes a sample app.

I hope you find our APM tool useful and easy to use.  
Eyal.

---

_[View the full topic](https://discuss.elastic.co/t/best-practice-for-apm/195646)._