<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

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

送信することにより、Elasticの<a href="/jp/legal/elastic-cloud-account-terms" target="_self">利用規約</a>を読み、同意したものと見なされます。また、上記で提供された連絡先に<a href="/jp/legal/privacy-statement#how-we-use-the-information" target="_self">特定の通知</a>が送信されることを認めたことになります。詳細については、<a href="/jp/legal/privacy-statement/" target="_self">Elasticのプライバシーポリシー</a>をご覧ください。これらの同意についてはいつでもオプトアウトすることが可能です。

By submitting you acknowledge that you've read and agree to our <a href="/legal/elastic-cloud-account-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.By submitting this form, I agree to Elastic sharing my contact information with Google Cloud. I also agree to Elastic giving my information to the vendor for the purpose of shipping my food package.

GDPR Text + Google Cloud

送信することにより、Elasticの<a href="/jp/legal/elastic-cloud-account-terms" target="_self">利用規約</a>を読み、同意したものと見なされます。また、関連する製品やサービスについて、上記で提供された情報を使用してElasticから<a href="/jp/legal/privacy-statement#how-we-use-the-information" target="_self">連絡する</a>場合があることを認めたことになります。詳細については、<a href="/jp/legal/privacy-statement/" target="_self">Elasticのプライバシー</a>ポリシーをご覧ください。これらの同意についてはいつでもオプトアウトすることが可能です。このフォームを送信することにより、Elasticが私の連絡先情報をGoogle Cloudに共有することに同意します。また、Elasticが私に食材パッケージを発送する目的で私の情報をベンダーに提供することにも同意します。

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

送信することにより、Elasticの<a href="/jp/legal/serverless-preview-terms" target="_self">利用規約</a>を読み、同意したものと見なされます。また、関連する製品やサービスについて、上記で提供された情報を使用してElasticから<a href="/jp/legal/privacy-statement#how-we-use-the-information" target="_self">連絡する</a>場合があることを認めたことになります。詳細については、<a href="/jp/legal/privacy-statement/" target="_self">Elasticのプライバシー</a>ポリシーをご覧ください。これらの同意についてはいつでもオプトアウトすることが可能です。

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

送信することにより、<a href="/jp/agreements/global/cloud-services-monthly" rel="nofollow">Elastic Cloud利用規約</a>に同意したものとみなされます。個人情報は<a href="/jp/legal/privacy-statement">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

送信することにより、Elasticの<a href="/jp/legal/terms-of-use" target="_self">利用規約</a>を読み、同意したものと見なされます。また、関連する製品やサービスについて、上記で提供された情報を使用してElasticから<a href="/jp/legal/privacy-statement#how-we-use-the-information" target="_self">連絡する</a>場合があることを認めたことになります。詳細については、<a href="/jp/legal/privacy-statement/" target="_self">Elasticのプライバシー</a>ポリシーをご覧ください。これらの同意についてはいつでもオプトアウトすることが可能です。

Explore similar demos

Overview

Speakers

Close

See more insights

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.

このページのコンテンツは、選択された言語ではご利用いただけません。Elasticでは現在、コンテンツをさまざまな言語でご利用いただけるよう取り組んでいます。お使いの言語が準備されるまでお待ちくださるようお願いいたします。

Author

Articles by

Watch now (no PT)

Watch now

See all top stories

すべてのトップストーリーを見る

All (no PT translation)

Contact information

Press Release

Share on Reddit

Share this story

Share by Email

Thank you for your interest!

Contact Info

Follow us on Youtube

Load More

Share on LinkedIn

Search Integrations

All Solutions

Video for

See when this webinar starts in my time zone

現在のタイムゾーンでこのウェビナー開始時間を見る

Register to Watch

See All Posts

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

他の予定と重なってしまった…という場合も、問題ありません。参加登録されると、録画配信をご利用いただけます。関連コンテンツのご案内もメールでお届けします。

Author

Articles by Sebastian Herzberg

How the Elastic Stack Keeps our Taxis Rolling

Sign up for Elastic Cloud free trial