<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Cem DURAK on Medium]]></title>
        <description><![CDATA[Stories by Cem DURAK on Medium]]></description>
        <link>https://medium.com/@cemdurak?source=rss-b8eab1d49ad------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xNmvEqCHCrxxOVafKfh1Lg@2x.jpeg</url>
            <title>Stories by Cem DURAK on Medium</title>
            <link>https://medium.com/@cemdurak?source=rss-b8eab1d49ad------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:14:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cemdurak/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Docker Engine Setup On Amd Chipset]]></title>
            <link>https://medium.com/@cemdurak/docker-engine-setup-on-amd-chipset-5069ffe523ee?source=rss-b8eab1d49ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/5069ffe523ee</guid>
            <dc:creator><![CDATA[Cem DURAK]]></dc:creator>
            <pubDate>Mon, 01 Dec 2025 16:13:17 GMT</pubDate>
            <atom:updated>2025-12-01T16:13:17.121Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are getting error on docker ce setup like</p><pre>Skipping acquire of configured file &#39;stable/binary-i386/Packages&#39; as repository &#39;https://download.docker.com/linux/ubuntu&#39; noble In Release&#39; doesn&#39;t support architecture &#39;i386&#39;</pre><p>Add `Architectures: amd64` to docker.sources file</p><pre>Types: deb<br>URIs: https://download.docker.com/linux/ubuntu<br>Suites: noble<br>Components: stable<br>Architectures: amd64<br>Signed-By: /etc/apt/keyrings/docker.asc</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5069ffe523ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MCP Managed Automated Browser]]></title>
            <link>https://medium.com/@cemdurak/mcp-managed-automated-browser-27b89529f99c?source=rss-b8eab1d49ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/27b89529f99c</guid>
            <category><![CDATA[mcp-server]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[browser-automation]]></category>
            <dc:creator><![CDATA[Cem DURAK]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 11:41:31 GMT</pubDate>
            <atom:updated>2025-08-04T11:41:31.257Z</atom:updated>
            <content:encoded><![CDATA[<h4>Remote Manageable Browser</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kGf2W6qjikWUPXD-2VUbMQ.png" /><figcaption>BrowserControl</figcaption></figure><p>Web automation has become an essential part of modern development workflows, from testing to scraping . While tools like Playwright have improved browser automation, integrating them into AI-powered workflows is still challenging.</p><p>In this article, I’ll walk you through building a containerized solution that combines Chromium browser with Playwright MCP , creating a powerful platform for AI-driven web interactions.</p><h3>Introduction to MCP</h3><p>The <strong>Model Context Protocol </strong>(MCP) is an open standart , developed by <strong>Antrophic</strong>, acts as a bridge between AI systems and the tools they need to execute tasks. Instead of AI models directly accessing external resources, MCP provides a structured interface that defines how requests are made, authenticated, and executed. This approach ensures security, consistency, and reliability when AI models need to interact with browsers , APIs, file systems or other external resources.</p><p>Also, enables AI models to safely extend their capabilities beyond text generation, allowing them to perform real-world actions through controlled interfaces.</p><h3><strong>What We’re Building</strong></h3><p>Our solution consists of two main components:</p><ul><li><strong>Containerized Chromium browser</strong> with remote debugging enabled</li><li><strong>Playwright MCP server</strong> that connects to the browser via Chrome DevTools Protocol</li></ul><p>This architecture allows AI models to control a real browser instance through standardized MCP commands, enabling complex web automation tasks.</p><h3><strong>Chrome DevTools Protocol</strong></h3><p>Chrome DevTools Protocol is a debugging protocol that allows external tools to communicate with Chrome/Chromium browsers. It’s the underlying technology that powers Chrome DevTools and enables programmatic control of browser behavior.</p><p>CDP uses a <strong>WebSocket</strong> connection to communicate between the client (in our case playwright-mcp) and the browser.</p><h3>Architecture</h3><h4>Directory Structure</h4><pre>browserControl/<br>  ├── compose.yml<br>  ├── Dockerfile<br>  ├── conf/<br>  │   └── autostart<br>  └── mcp/<br>      ├── main.ts<br>      ├── server.ts<br>      ├── transport.ts<br>      ├── dnsResolve.ts<br>      └── package.json</pre><h4>Containerized Browser</h4><p>Browser container is built on LinuxServer’s Chromium image, which provides a web-accessible browser interface. Allow you to see your prompts in action.</p><p>The tricky part is enabling CDP (Chrome DevTools Protocol) connections through <strong>remote debugging</strong> on port 9222 for programmatic access.</p><h4>Playwright MCP</h4><p>Instead of the usual playwright connection, our Playwright MCP connects to the browser via the <strong>Chrome DevTools Protocol</strong>, enabling real-time browser control through standardized MCP interfaces.</p><h3>Bundling MCP and Browser</h3><p>Docker allows us to bundle the browser with MCP by building on top of an existing browser image and adding the MCP components.</p><h4>Dockerfile:</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8afe724f3a98984f6d2eb4d3f63d3cba/href">https://medium.com/media/8afe724f3a98984f6d2eb4d3f63d3cba/href</a></iframe><h4>compose.yml:</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/47b5083a60ba1db899e0e2167027383a/href">https://medium.com/media/47b5083a60ba1db899e0e2167027383a/href</a></iframe><h4>Setting Up the Project In Seconds</h4><p>Start by cloning the repository. After that, just run `docker compose up` to launch the project.</p><pre>git clone https://github.com/cemdrk/browser-control.git<br>cd browser-control<br><br># Start browser control<br>docker compose up<br><br># Stop <br>docker compose down</pre><h4>Connecting MCP Clients</h4><p>Here’s an example configuration for Cursor using the Streamable HTTP transport. To use the legacy HTTP+SSE transport instead, simply change the endpoint to /sse.</p><pre>{<br>  &quot;mcpServers&quot;: {<br>    &quot;browserControl&quot;: {<br>      &quot;url&quot;: &quot;http://127.0.0.1:8000/mcp&quot;<br>    }<br>  }<br>}</pre><h4>Port Conflicts</h4><p>Ensure that ports <strong>3000</strong> and <strong>8000</strong> are free on your host system. If they’re in use, update compose.yml with available ports.</p><h4>Real-World Applications</h4><p>This setup enables powerful AI-driven web automation scenarios:</p><ul><li><strong>Automated Testing</strong>: AI models can write and execute complete test suites</li><li><strong>Data Extraction</strong>: Intelligent data extraction of dynamic web content</li><li><strong>User Journey Simulation</strong>: Realistic user behavior testing</li></ul><h3><strong>In Action 👀</strong></h3><p>In this scenario, the browser was instructed to navigate to a specific URL, search for ‘MacBook’ products, and add the second item from the search results to the cart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*px8LHqwMgSUQM-PHhGp9gw.gif" /><figcaption>browser inception</figcaption></figure><h3>Bonus 🎉</h3><p>As you may have noticed, this project also supports controlling your local browser. You just need to start your browser with the debugging port enabled.</p><p>Example terminal command for mac users:</p><pre>/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \<br>--remote-debugging-port=9222 --user-data-dir=$HOME/Desktop/chromeUser \<br> --no-first-run </pre><p>Then uncomment <strong>MCP_CDP_ENDPOINT</strong> environment variable in compose.yml file .<br>It should look like :</p><pre>services:<br>  browsercontrol:<br>    build: .<br>    environment:<br>      - TZ=Europe/Istanbul<br>      - CHROME_CLI=--remote-debugging-port=9222<br>      - MCP_CDP_ENDPOINT=http://host.docker.internal:9222 # local browser access<br>    ports:<br>      - &quot;127.0.0.1:3000:3000&quot; # HTTP Chromium desktop gui<br>      - &quot;127.0.0.1:8000:8000&quot;<br>    volumes:<br>      - ./mcp:/.app<br>      - /.app/node_modules<br>    extra_hosts:<br>      - &quot;host.docker.internal:host-gateway&quot;</pre><p>After providing this configuration, you should be able to control your browser using prompts.<br>Note that the browser must be Chromium-based due to the use of the Chrome DevTools Protocol.</p><h3>Conclusion</h3><p>By combining containerized Chromium with Playwright MCP integration, we’ve created a powerful platform for AI-driven web automation. This architecture provides flexibility and scalability needed for modern web automation workflows while maintaining the simplicity required for rapid development and deployment.</p><p>The complete source code is available to help you get started with your own AI-powered web automation projects.</p><p><a href="https://github.com/cemdrk/browser-control">GitHub - cemdrk/browser-control: Containerized Browser Manageable via MCP</a></p><p>Whether you’re building automated testing frameworks, or intelligent web scrapers this containerized approach provides a solid foundation for your next project.</p><p>Just clone the repository and run `docker compose up` to have your containerized browser automation environment running in seconds.</p><h4>References</h4><ul><li><a href="https://github.com/microsoft/playwright-mcp">Playwright MCP</a></li><li><a href="https://docs.linuxserver.io/images/docker-chromium/">LinuxServer.io — Chromium</a></li><li><a href="https://chromedevtools.github.io/devtools-protocol">Chrome DevTools Protocol</a></li><li><a href="https://modelcontextprotocol.io/specification/2025-03-26/basic/transports">MCP Transports</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27b89529f99c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Executing NodeJS Tasks Using Apache Airflow]]></title>
            <link>https://medium.com/@cemdurak/executing-nodejs-tasks-using-apache-airflow-1f1924d788de?source=rss-b8eab1d49ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f1924d788de</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[airflow]]></category>
            <dc:creator><![CDATA[Cem DURAK]]></dc:creator>
            <pubDate>Fri, 02 Aug 2024 08:32:42 GMT</pubDate>
            <atom:updated>2024-08-02T08:34:03.824Z</atom:updated>
            <content:encoded><![CDATA[<h4>with KubernetesPodOperator</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rKtbiFLjxCz4AkPX" /><figcaption>Photo by <a href="https://unsplash.com/@carrier_lost?utm_source=medium&amp;utm_medium=referral">Ian Taylor</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Recently, I needed to migrate NodeJS tasks from <a href="https://github.com/agenda/agendash">Agendash</a> to Airflow without rewriting them in Python. I came across the KubernetesPodOperator, which offers a way to run NodeJS tasks within Airflow by utilizing Kubernetes pods.</p><p>Here my solution :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/829767f06b5cd2e0548264d3be1e834f/href">https://medium.com/media/829767f06b5cd2e0548264d3be1e834f/href</a></iframe><p>Hopefully, this template was useful for you too. I would love to hear about alternative methods or improvements that you may have.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f1924d788de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Alembic Existing DB]]></title>
            <link>https://medium.com/@cemdurak/alembic-existing-db-a4cf36a33c77?source=rss-b8eab1d49ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4cf36a33c77</guid>
            <category><![CDATA[postgres]]></category>
            <category><![CDATA[alembic]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[data-migration-management]]></category>
            <dc:creator><![CDATA[Cem DURAK]]></dc:creator>
            <pubDate>Mon, 17 Oct 2022 06:55:47 GMT</pubDate>
            <atom:updated>2022-10-17T06:55:47.369Z</atom:updated>
            <content:encoded><![CDATA[<h3>Alembic for Existing DB</h3><p>An easy way to implement migration management</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RqQefdRfXGq7ozjr" /><figcaption>Photo by <a href="https://unsplash.com/@campaign_creators?utm_source=medium&amp;utm_medium=referral">Campaign Creators</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Let’s say you want to add migration management to your python project at some point after your DB has already been created. Alembic might help you.</p><p><strong>alembic</strong> is the most known migration management tool for python projects. Usually, it is used for automating DB migration with SQLAlchemy ORM. However, it also supports use with the already existing DB.</p><h4>Installation</h4><p>Alembic package can be installed via pip. Currently stable version <strong>1.8.1</strong></p><pre>$ pip install alembic</pre><h4>Initialization</h4><p>Before creating migration files it needs some config files. In order to create these files, run the following command.</p><pre>$ alembic init migrations</pre><p>This command is going to create alembic initial files shown below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*iQRd6UL7GVLNI7S4p7LGlg.png" /></figure><h4>Configuration</h4><p>Alembic needs your <strong>DB URI</strong> to run its commands.Add <strong>set_main_option</strong> to migrations / env.py file. It should be under <strong>contex.config</strong> line.</p><pre>config = context.config<br>config.set_main_option(‘sqlalchemy.url’, os.environ[‘DB_URI’])</pre><p>Specific to Postgre DB, inside the <strong>run_migrations_offline</strong> function schema info should be added as well.</p><pre>context.configure( <br> version_table_schema=’public’, <em># your schema name</em><br> <em># other params </em><br>)</pre><h4>Preparing DB</h4><p>Check if alembic connects to your DB.</p><pre>$ alembic current</pre><p>Create alembic version table on your DB</p><pre>$ alembic upgrade head</pre><p>After running the above command, a new table named <strong>alembic_version</strong> is going to be created.</p><h4>Getting current DB structure</h4><p>One of the easy way to get the current DB structure is to create a dump file as <strong>.sql. </strong>Run the following command to get current tables on your DB.</p><pre>$ pg_dump -U postgres -O -s -f initial.sql</pre><p>After getting the dump file you need to store it on your project. In our case, it is stored under the <strong>migrations</strong> folder.</p><h4>Creating first revision</h4><p>To keep the current status as an alembic revision:</p><pre>$ alembic revision -m “initial”</pre><p>This command is going to create a new version file under <strong>migrations / versions</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/814/1*nAfzS_8EAg0yPt4S3nrPOw.png" /></figure><p>Edit your version file and add execute command inside the <strong>upgrade</strong> function:</p><pre>def upgrade() -&gt; None:<br>    with open(‘migrations/initial.sql’) as file:<br>    op.execute(file.read())</pre><p>Lastly, pin the current status:</p><pre>$ alembic stamp &lt;revision_id&gt;</pre><p>After running `<strong>stamp`</strong> command, alembic will be ready for adding new revisions.</p><p>Hopefully, this post is useful to you. See you in the next posts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4cf36a33c77" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Elasticsearch — Search Templates]]></title>
            <link>https://medium.com/blutv/elasticsearch-search-templates-a77025095073?source=rss-b8eab1d49ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/a77025095073</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[elasticsearch]]></category>
            <category><![CDATA[elasticsearch-queries]]></category>
            <category><![CDATA[elk-stack]]></category>
            <category><![CDATA[kibana]]></category>
            <dc:creator><![CDATA[Cem DURAK]]></dc:creator>
            <pubDate>Mon, 13 Sep 2021 08:00:07 GMT</pubDate>
            <atom:updated>2021-09-13T08:00:07.368Z</atom:updated>
            <content:encoded><![CDATA[<h3>Elasticsearch — Search Templates</h3><p>Merhaba 👋 , bu yazımda Elasticsearch kullanımında yeni karşılaştığım Search Template özelliğinin nasıl kullanılabileceği ve getirdiği avantajları anlatmaya çalışacağım.</p><p>Örneklerle anlatabilmek icin bu özelliğin kullanıldığı ve kullanılmadığı durumları basit bir senaryo ile inceleyeceğiz. Klasik şekilde, örneklerden önce tanım ile başlayalım!</p><p><strong>Search Template Nedir?</strong></p><p>Search Template, search sorgularını şablon halinde sunucularda kaydedebilmeyi ve kaydettiğimiz şablon sorguyu farklı değişkenler ile çalıştırmayı sağlayan Elasticsearch özelliğidir.</p><p><strong>Senaryo Hazırlık</strong></p><p>Sorgulama aşamasına geçmeden önce veritabanımızı hazırlayalım. Bu aşamada Docker kullanmak işimizi kolaylaştıracaktır.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4fdfce639440dfef37375d5f497990fa/href">https://medium.com/media/4fdfce639440dfef37375d5f497990fa/href</a></iframe><p>Kibana burada isteğe bağlı. Kibana’nın Dev Tools arayüzü Elasticsearch isteklerini kolayca gönderebileceğimiz ortam sağlıyor. curl ile terminal üzerinden de bu istekler gönderilebilir.</p><figure><img alt="kibana-dev-tools" src="https://cdn-images-1.medium.com/max/544/1*0Z0T3Cu5QzQZz5u5zwxBqA.png" /></figure><p>Senaryomuzda film, dizi gibi izlenebilir içeriklerimizi Elasticsearch’e kaydedip sorgulayacağız. Bunun için index’e ihtiyacımız var. Index oluşturmak için:</p><pre>PUT contents</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*iAzSyfGjAHlgFfZ3sG3GGA.png" /></figure><p>İçeriğin başlığı, tipi, türü ve izlenme sayısı Elasticsearch’te kayıtlı olsun:</p><pre>PUT contents/_mapping<br>{<br>  &quot;properties&quot;: {<br>    &quot;title&quot;: {<br>      &quot;type&quot;: &quot;text&quot;<br>    },<br>    &quot;content_type&quot;: {<br>      &quot;type&quot;: &quot;keyword&quot;<br>    },<br>    &quot;genre&quot;: {<br>      &quot;type&quot;: &quot;keyword&quot;<br>    },<br>    &quot;view_count&quot;: {<br>      &quot;type&quot;: &quot;integer&quot;<br>    }<br>  }<br>}</pre><p>Örnek içerik verisi:</p><pre>{<br>  &quot;title&quot;: &quot;Movie Watched By a Thousand&quot;,<br>  &quot;content_type&quot;: &quot;movie&quot;,<br>  &quot;genre&quot;: &quot;action&quot;,<br>  &quot;view_count&quot;: 1000<br>}</pre><p>Bundan önceki komutları Kibana ile yaptık. curl kullanımına örnek olması açısından içeriği curl ile ekleyelim:</p><pre>curl -H &quot;Content-Type:application/json&quot; -XPOST localhost:9200/contents/_doc -d &#39;{&quot;title&quot;:&quot;Movie Watched By a Thousand&quot;,&quot;content_type&quot;:&quot;movie&quot;,&quot;genre&quot;:&quot;action&quot;,&quot;view_count&quot;:1000}&#39;</pre><p>Veritabanını hazırlama aşamasını bitirmiş olduk.Sorgulama aşamasına geçebiliriz.</p><p><strong>Template kullanmadığımızda nasıl sorgularız?</strong></p><p>Aksiyon filmlerini izlenilenme sayılarına göre, en çok izlenilen ilk sırada gelecek şekilde sıralamak istiyorsak template kullanmadığımız durumda Elasticsearch’e gidecek istek şöyle olmalı:</p><pre>GET /contents/_search<br>{<br>  &quot;query&quot;: {<br>    &quot;bool&quot;: {<br>      &quot;must&quot;: [<br>        {<br>          &quot;match&quot;: {<br>            &quot;content_type&quot;: &quot;movie&quot;<br>          }<br>        },<br>        {<br>          &quot;match&quot;: {<br>            &quot;genre&quot;: &quot;action&quot;<br>          }<br>        }<br>      ]<br>    }<br>  },<br>  &quot;sort&quot;: [<br>    {<br>      &quot;view_count&quot;: {<br>        &quot;order&quot;: &quot;desc&quot;<br>      }<br>    }<br>  ]<br>}</pre><p><strong>Template tanımlamış olsaydık nasıl sorgu gönderirdik?</strong></p><p>Tanımlayacağımız template istenilen içerik tip, tür ve sıralama değerlerini parametrik olarak almalı. Gönderilen parametrelere göre içerikler üzerinde filtreleme ve sıralama yapmalı.</p><pre>PUT _scripts/sort-contents<br>{<br>  &quot;script&quot;: {<br>    &quot;lang&quot;: &quot;mustache&quot;,<br>    &quot;source&quot;: {<br>      &quot;query&quot;: {<br>        &quot;bool&quot;: {<br>          &quot;must&quot;: [<br>            {<br>              &quot;match&quot;: {<br>                &quot;content_type&quot;: &quot;{{content_type}}&quot;<br>              }<br>            },<br>            {<br>              &quot;match&quot;: {<br>                &quot;genre&quot;: &quot;{{genre}}&quot;<br>              }<br>            }<br>          ]<br>        }<br>      },<br>      &quot;sort&quot;: [<br>        {<br>          &quot;{{sort}}&quot;: &quot;{{order}}&quot;<br>        }<br>      ]<br>    }<br>  }<br>}</pre><p>Göndermiş olduğumuz istek ile sort-contents isimli bir template tanımlanmış oldu.Template tanımladıktan sonra aksiyon filmlerini çektiğimiz sorgunun son hali:</p><pre>POST /contents/_search/template<br>{<br>  &quot;id&quot;: &quot;sort-contents&quot;,<br>  &quot;params&quot;: {<br>    &quot;content_type&quot;: &quot;movie&quot;,<br>    &quot;genre&quot;: &quot;action&quot;,<br>    &quot;sort&quot;: &quot;view_count&quot;,<br>    &quot;order&quot;: &quot;desc&quot;<br>  }<br>}</pre><p>Python client örneği:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/75118eb1902bb1cd072de4664320eaf0/href">https://medium.com/media/75118eb1902bb1cd072de4664320eaf0/href</a></iframe><p><strong>Sonuç</strong></p><p>Template kullandığımızda sorgunun yapısı Elasticsearch’te saklandığı için uygulama kodları sorgu dili ile uğraşmadan sadece değişkenleri ileterek sorgulayabiliyor.</p><p>Sorgunun Elasticsearch’te saklanması, sorguda değişiklik gerektiği durumda uygulama kodlarını degiştirmeden bu değişikliği yapabilme esnekliğini de bize getiriyor.</p><p>Gönderilen isteklerde taşınan verinin boyutu ve karmaşıklığı göz önüne alındığında template kullanmak daha basit ve küçük boyutlarda veri taşımamızı sağlıyor. Taşınan verinin boyutuna göre ücretlendirme yapılan cloud dünyasında, sunuculara yapılan istek sayısı ne kadar fazla ise template kullanmanın önemi o kadar artıyor.</p><p>Umarım sizin için de faydalı olmuştur. Bir sonraki yazıda görüşmek üzere!</p><ul><li><a href="https://github.com/cemdrk/es-search-template">GitHub - cemdrk/es-search-template</a></li><li><a href="https://www.elastic.co/guide/en/elasticsearch/reference/7.14/search-template.html">Search templates | Elasticsearch Guide [7.14] | Elastic</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a77025095073" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blutv/elasticsearch-search-templates-a77025095073">Elasticsearch — Search Templates</a> was originally published in <a href="https://medium.com/blutv">blutv</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>