<img src="https://api.contentstack.io/v2/assets/575e4cef3dc542cb38c09329/download?uid=blt0c4ab6c5c3b557f7?uid=blt0c4ab6c5c3b557f7" data-sys-asset-uid="blt45fd4001b2df7f93" alt="mytaxi_logo" width="207" height="92" style="float: right;width: 207;height: 92;margin: 0px;text-align: right;"/><blockquote class="summary">The Elastic technology stack supports our business in two different areas. It&nbsp;keeps our app responsive as a cache and also&nbsp;provides a backend for an intense amount of logs. This article will outline the&nbsp;architecture of our Logging Cluster. <a href="https://mytaxi.com/index.html">Mytaxi</a> is currently Europe’s most successful taxi app. Everyday we connect thousands of customers with professional taxi-drivers. Booking, procuration and payment have to run fast and smooth 24/7.</blockquote><h2>The Logging-Cluster</h2>We started out in 2013 with a pretty simple standard configuration of the Elastic technology stack. It had two Elasticsearch nodes and one node for Logstash and Kibana. This worked well back in the days before our exponential growth started in 2014. This setup was running until mid 2015. The cluster was abandoned during our growth phase and thus it was lacking performance. By mid 2015 we had about 2 TB of data stored in Elasticsearch.Also, in 2013 we decided to move away from a monolithic backend structure towards microservices. By now we have split our backend into around 50 microservices. We needed to gather logs from all of these services in one place. By July 2015 we decided to set up a new cluster that would support our needs for the upcoming years. The requirements were: <ul><li>Save our logs for 90 days (a day is ~40 GB worth of logs)</li><li>Read performance was a bottleneck when people query large time ranges for data. We wanted to increase the performance by having more nodes.</li><li>The number of shards is configured during cluster creation. It cannot be changed. We wanted to have a number that is evenly divisible by 2, 4, 5 and 10. The least common multiple is 20.</li><li>Each worker should manage an even number of shards.</li><li>Although money is not the main focus, we wanted to reach a price/performance maximum.</li></ul><h2>Hardware setup and installation procedure</h2>With these requirements we went to AWS and checked for a reasonable instance size. Three instance sizes were in line with our requirements (prices may be outdated):<ul><li>i2.xlarge - 4 CPUs, 30,5 GB RAM, 800 GB SSD - 686,62 $/month</li><li>i2.2xlarge - 8 CPUs, 60,5 GB RAM, 2x800 GB SSD - 1510,57 $/month</li><li>m1.xlarge - 4 CPUs, 15 GB RAM, 4x420 GB HDD - 277,43 $/month</li></ul>The m1.xlarge seemed to be gold here. They are cheap and they have 4 HDDs which could be combined to a RAID0. Ten m1.xlarge instances would form a cluster with 150 GB RAM and 16,8 TB of disk. With this much disk we could easily increase the amount of time that we keep the logs.To configure ten nodes and install an equal configuration of Elasticsearch, we used Ansible. The playbook combined roles for:<ul><li>Bootstrapping the AWS instance (setup hostname, install common packages etc.)</li><li>Setting up a RAID0 in software</li><li>Installing a monitoring software that reports to a monitoring proxy in the same VPC</li><li>Connecting the instances to our directory server, so that backend engineers can log in via SSH</li><li>Installing and configuring Elasticsearch including several plugin</li></ul><h2>Logcluster architecture</h2>With 10 Elasticsearch nodes running, you might wonder what the whole system looks like. Our microservices report their application logs into an AWS Elasticache (Redis). Logstash will pick up the logs from there and process them. The image below gives an overview of the architecture<img src="https://api.contentstack.io/v2/assets/575e4cef3dc542cb38c0934a/download?uid=blt94bf10fa2418bd38?uid=blt94bf10fa2418bd38" data-sys-asset-uid="blt32f77ed8b41f7b57" alt="logcluster.png" style="max-width: 100%;"/>&nbsp;<h2>Logcluster usage examples</h2>At the beginning of November 2015 we decided to push through a large change in our backend architecture. We started to set up every one of our microservices in a Docker container running on an AWS ECS cluster. This major change was accompanied by our Logcluster. As the migration needed to be performed without service interruption, we followed the Kibana screens closely. Even the tiniest amount of increased exception rates from an application, could indicate problems in the live service. So after we started containers for a new service, everyone would stare at the large TV set that shows Kibana and they would cheer when there were no exceptions. Although we were a bit frightened when batman showed up...<img src="https://api.contentstack.io/v2/assets/575e4cef12798d8e381fe673/download?uid=blt7d7204806603f32d?uid=blt7d7204806603f32d" data-sys-asset-uid="blt3b872bba91fd22d3" alt="kibana_batman.png" style="max-width: 100%;"/><h2>Conclusion</h2>It is our goal to provide the best taxi experience in Europe and expand our service to do more and more cities over the next years. With around 50 microservices we need an information hub to get an overview of the overall system status. For us the Elastic-Technology-Stack provides this overview. But it also gives developers the chance to dig deep into bugs and closely follow the impact of changes. <img src="https://api.contentstack.io/v2/assets/575e4cef58208ba076e29117/download?uid=blt2ab3600475ffc077?uid=blt2ab3600475ffc077" data-sys-asset-uid="blt3c3099a8fed129d9" alt="Sebastian_Headshot.png" style="float: left;margin: 0px;text-align: left;"/>Sebastian Herzberg is a system &amp; network engineer at Intelligent Apps GmbH&nbsp;(mytaxi) in Hamburg, where he started in May 2015. During the last months he has been working on projects involving a new monitoring system and the migration to Docker. He is mainly involved with the backend systems running on AWS together with a team of 3 system administrators and 2 backend engineers.

taxis-people-waiting.jpg

taxi-ihr-fahrer-mobile-phone.jpg

How the Elastic Stack Keeps our Taxis Rolling

Start free trial

Blog Footer CTA

Sign up for Elastic Cloud free trial

Sebastian Herzberg

The content on this page is not available in the selected language. As Elastic grows globally, we continue to support content in multiple languages.

The content on this page is not available in the selected language.

El contenido de esta página no está disponible en el idioma seleccionado. Elastic está trabajando para garantizar que el contenido esté disponible en varios idiomas. Gracias por tu paciencia mientras trabajamos.

By submitting you acknowledge that you've read and agree to our <a href="/legal/elastic-cloud-account-terms" target="_self">Terms of Service</a>, and you agree to receive the <a href="/legal/privacy-statement#how-we-use-the-information" target="_self">selected communications</a> at the contact details you provided above. See <a href="/legal/privacy-statement/" target="_self">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Communication Preferences - ONLY for /communication-preferences

Al enviar, confirma que ha leído y acepta nuestras <a href="/es/legal/elastic-cloud-account-terms" target="_self">Condiciones de servicio</a>, y que acepta recibir las <a href="/es/legal/privacy-statement#how-we-use-the-information" target="_self">comunicaciones seleccionadas</a> en los detalles de contacto que proporcionó anteriormente. Consulte la <a href="/es/legal/privacy-statement/" target="_self">Declaración de privacidad de Elastic</a> para obtener más información o para cancelar su suscripción en cualquier momento.

By submitting you acknowledge that you've read and agree to our <a href="/legal/serverless-preview-terms" target="_blank">Terms of Service</a>, and that Elastic may <a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">contact you</a> about our related products and services, using the details you provide above. See <a href="/legal/privacy-statement/" target="_blank">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Serverless GDPR Text

Al enviar, confirma que ha leído y acepta nuestras <a href="/es/legal/serverless-preview-terms" target="_self">Condiciones de servicio</a>, y que Elastic puede <a href="/es/legal/privacy-statement#how-we-use-the-information" target="_self">ponerse en contacto con usted</a> acerca de nuestros productos y servicios relacionados. Consulte la <a href="/es/legal/privacy-statement/" target="_self">Declaración de privacidad de Elastic</a> para obtener más información o para cancelar su suscripción en cualquier momento.

By submitting you agree to <a href="/agreements/global/cloud-services-monthly" rel="nofollow">Elastic Cloud Terms of Service</a>. Your personal data will be processed in accordance with <a href="/legal/privacy-statement">Elastic's Privacy Statement</a>.

Cloud Trial GDPR Text

Al enviar esta información, aceptas los <a href="/es/agreements/global/cloud-services-monthly" rel="nofollow">Términos de servicio de Elastic</a>. Los datos personales se procesarán de conformidad con la <a href="/es/legal/privacy-statement">declaración de privacidad de Elastic</a>.

By submitting you acknowledge that you've read and agree to our <a href="/legal/terms-of-use" target="_blank">Terms of Service</a>, and that Elastic may <a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">contact you</a> about our related products and services, using the details you provide above. See <a href="/legal/privacy-statement/" target="_blank">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Newsletter GDPR Text

Al enviar, confirma que ha leído y acepta nuestras <a href="/es/legal/terms-of-use" target="_self">Condiciones de servicio</a>, y que Elastic puede <a href="/es/legal/privacy-statement#how-we-use-the-information" target="_self">ponerse en contacto con usted</a> acerca de nuestros productos y servicios relacionados. Consulte la <a href="/es/legal/privacy-statement/" target="_self">Declaración de privacidad de Elastic</a> para obtener más información o para cancelar su suscripción en cualquier momento.

Hosted by

All Solutions

Follow us on Youtube

Watch now (no PT)

Articles by

Share by Email

Filters

All (no PT translation)

Contact information

See when this webinar starts in my time zone

Ver cuándo comienza este webinar en mi zona horaria

Thank you for your interest!

Register to Attend

Small image for

Register to Watch

Continue reading

Featured webinar

What to explore next...

Reset all

Load more press releases

Sign In to Attend

Share

Upcoming webinar

Learn more

Search Integrations

Share on Reddit

Share on Twitter

Share on Facebook

Load more news

View more posts

On-demand webinar

Follow us on Facebook

Author

Press Release

You'll also receive an email with related content.

You'll also receive an email with related content

Además, te enviaremos contenidos relevantes

Print

Contact Info

Overview

Video for

Read less

Register now

Share this story

See All Posts

See all top stories

View next

Can't make it? Register and we'll send you the recording. You'll also receive an email with related content

¿No puedes asistir? Regístrate y te enviaremos la grabación. También recibirás un correo electrónico con contenido relacionado.

Follow us on LinkedIn

Highlights

Explore similar demos

Follow us on Twitter

Share on LinkedIn

Load More

See more insights

Speakers

Close

Thank you for registering. We will send you a confirmation email soon.

Gracias por registrarte. Te enviaremos un correo electrónico de confirmación pronto.

Author

Articles by Sebastian Herzberg

How the Elastic Stack Keeps our Taxis Rolling

Sign up for Elastic Cloud free trial