<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Aditya Pandey</title>
    <description>The latest articles on DEV Community by Aditya Pandey (@thepracticaldev_1511).</description>
    <link>https://dev.to/thepracticaldev_1511</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1253941%2F5c43743e-d131-4127-be80-70a6c3aff7b4.JPEG</url>
      <title>DEV Community: Aditya Pandey</title>
      <link>https://dev.to/thepracticaldev_1511</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/thepracticaldev_1511"/>
    <language>en</language>
    <item>
      <title>REST vs GraphQL</title>
      <dc:creator>Aditya Pandey</dc:creator>
      <pubDate>Tue, 16 Jan 2024 05:50:47 +0000</pubDate>
      <link>https://dev.to/thepracticaldev_1511/rest-api-vs-graphql-4b37</link>
      <guid>https://dev.to/thepracticaldev_1511/rest-api-vs-graphql-4b37</guid>
      <description>&lt;p&gt;Each has advantages and disadvantages, or strengths and weaknesses, in terms of API architecture, when it comes to &lt;strong&gt;REST&lt;/strong&gt; and &lt;strong&gt;GraphQL&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--tFztnYy6--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_66%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/0owntgmgj37jbvlv6foi.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--tFztnYy6--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_66%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/0owntgmgj37jbvlv6foi.gif" alt="'REST VS GraphQL'" width="800" height="1040"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Below is the strength and weakness for both REST and GraphQL.&lt;/p&gt;

&lt;h2&gt;
  
  
  REST
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Works well when you need straightforward, consistent interfaces between different services or applications. - Uses standard HTTP methods like GET, POST, PUT, and DELETE for CRUD operations.&lt;/li&gt;
&lt;li&gt;Implementing caching strategies is simple.&lt;/li&gt;
&lt;li&gt;The drawback is that gathering relevant data from various endpoints might necessitate making several round trips.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  GraphQL
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Gives clients access to a single endpoint where they can query for the exact data they require.&lt;/li&gt;
&lt;li&gt;In nested queries, clients define the precise fields they need, and the server returns optimised payloads with only those fields.&lt;/li&gt;
&lt;li&gt;Allows subscriptions for in-the-moment notifications and mutations for changing data.
Excellent at combining data from several sources and adapting quickly to changing front-end needs.&lt;/li&gt;
&lt;li&gt;But if not adequately protected, it transfers complexity to the client side and opens the door to abusive inquiries. Compared to REST, caching strategies can be more intricate.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Conclusion -&lt;br&gt;
The particular needs of the application and development team will determine which of REST and GraphQL is the better option. REST is more appropriate for applications where clear and unambiguous contracts are desired, whereas GraphQL is a better fit for complicated or dynamic frontend requirements.&lt;/p&gt;




&lt;p&gt;If you have any questions, please feel free to ask.&lt;/p&gt;

&lt;p&gt;Feel free to share any thoughts or opinions or questions, I will be happy to help you as I can, Thanks for reading!&lt;/p&gt;

&lt;p&gt;If you are interested in web development, you can connect with me (&lt;a href="https://www.linkedin.com/in/aditya-pandey-40990a1b8/"&gt;https://www.linkedin.com/in/aditya-pandey-40990a1b8/&lt;/a&gt;).&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>productivity</category>
      <category>learning</category>
      <category>api</category>
    </item>
    <item>
      <title>What is Elastic Search ?</title>
      <dc:creator>Aditya Pandey</dc:creator>
      <pubDate>Thu, 11 Jan 2024 06:14:16 +0000</pubDate>
      <link>https://dev.to/thepracticaldev_1511/what-is-elastic-search--217</link>
      <guid>https://dev.to/thepracticaldev_1511/what-is-elastic-search--217</guid>
      <description>&lt;p&gt;&lt;strong&gt;Elasticsearch&lt;/strong&gt; is a distributed, free and open search and analytics engine for all types of data, including textual, numerical, geo-spatial, structured, and unstructured. Elasticsearch is built on Apache Lucene and was first released in 2010 by Elasticsearch N.V. (now known as Elastic). Known for its simple REST APIs, distributed nature, speed, and scalability, Elasticsearch is the central component of the Elastic Stack, a set of free and open tools for data ingestion, enrichment, storage, analysis, and visualization. Commonly referred to as the ELK Stack (after Elasticsearch, Logstash, and Kibana), the Elastic Stack now includes a rich collection of lightweight shipping agents known as Beats for sending data to Elasticsearch.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Elastic Search ?
&lt;/h2&gt;

&lt;p&gt;It is because users are forever searching weather it is an e-commerce site, social media handle or anything else.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Elasticsearch is fast. Because Elasticsearch is built on top of Lucene, it excels at full-text search. Elasticsearch is also a near real-time search platform, meaning the latency from the time a document is indexed until it becomes searchable is very short — typically one second. As a result, Elasticsearch is well suited for time-sensitive use cases such as security analytics and infrastructure monitoring.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Elasticsearch is distributed by nature. The documents stored in Elasticsearch are distributed across different containers known as shards, which are duplicated to provide redundant copies of the data in case of hardware failure. The distributed nature of Elasticsearch allows it to scale out to hundreds (or even thousands) of servers and handle petabytes of data.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Features of Elastic Search
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Distributed&lt;/li&gt;
&lt;li&gt;Open-source&lt;/li&gt;
&lt;li&gt;NoSQL&lt;/li&gt;
&lt;li&gt;JSON based&lt;/li&gt;
&lt;li&gt;RESTful&lt;/li&gt;
&lt;li&gt;Logs, Metrices&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  How does Elastic Search works ?
&lt;/h2&gt;

&lt;p&gt;Raw data flows into Elasticsearch from a variety of sources, including logs, system metrics, and web applications. Data ingestion is the process by which this raw data is parsed, normalized, and enriched before it is indexed in Elasticsearch. Once indexed in Elasticsearch, users can run complex queries against their data and use aggregations to retrieve complex summaries of their data. From Kibana, users can create powerful visualizations of their data, share dashboards, and manage the Elastic Stack.&lt;/p&gt;

&lt;h2&gt;
  
  
  What programming languages does Elasticsearch support?
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Java&lt;/li&gt;
&lt;li&gt;JavaScript (Node.js)&lt;/li&gt;
&lt;li&gt;Go&lt;/li&gt;
&lt;li&gt;.NET (C#)&lt;/li&gt;
&lt;li&gt;PHP&lt;/li&gt;
&lt;li&gt;Perl&lt;/li&gt;
&lt;li&gt;Python&lt;/li&gt;
&lt;li&gt;Ruby&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you have any questions, please feel free to ask.&lt;/p&gt;

&lt;p&gt;Feel free to share any thoughts or opinions or questions, I will be happy to help you as I can, Thanks for reading!&lt;/p&gt;

&lt;p&gt;If you are interested in web development, you can connect with me (&lt;a href="https://www.linkedin.com/in/aditya-pandey-40990a1b8/"&gt;https://www.linkedin.com/in/aditya-pandey-40990a1b8/&lt;/a&gt;).&lt;/p&gt;

</description>
      <category>elasticsearch</category>
      <category>webdev</category>
      <category>javascript</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
