# How to avoid problems with Perfomance, scalability and availability?

**URL:** <https://discuss.elastic.co/t/how-to-avoid-problems-with-perfomance-scalability-and-availability/8554>\
**Category:** Elasticsearch\
**Created:** [July 28, 2012, 11:44pm UTC](https://discuss.elastic.co/t/how-to-avoid-problems-with-perfomance-scalability-and-availability/8554 "2012-07-28T23:44:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vinicius\_Melo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinicius_melo/32/2720_2.png) [@Vinicius\_Melo](https://discuss.elastic.co/u/Vinicius_Melo)\
**Post date:** [July 28, 2012, 11:44pm UTC](https://discuss.elastic.co/t/how-to-avoid-problems-with-perfomance-scalability-and-availability/8554/1 "2012-07-28T23:44:34Z")

</div>

Hello,

We are building a product that will be a free social platform intended for  
knowledge exchange.

We have used the following databases together to deal with our problems:

- Users - DynamoDB
- Content and Search - ElasticSearch (lucene)
- Complicated machine learning processing, and custom algorithms - Redis

What do you think about it ? Which problems could we have with perfomance,  
scalability and availability? What can we do to avoid it?

We will contribute with Elastic-Search creating a lot of tutorials and wiki  
when we launch in our platform for free, if you are interested, please join  
our community: [http://www.guchex.com](http://www.guchex.com)

Thanks,

Vinicius Melo

---

<div class="post-metadata">

**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:18am UTC](https://discuss.elastic.co/t/how-to-avoid-problems-with-perfomance-scalability-and-availability/8554/2 "2017-07-06T03:18:35Z")

</div>

Closed on July 6, 2017, 3:18am UTC