<?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: Eládio Tchiinhemba</title>
    <description>The latest articles on DEV Community by Eládio Tchiinhemba (@tchiinhemba).</description>
    <link>https://dev.to/tchiinhemba</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%2F626559%2F96c44aa2-6152-4996-a89b-8cc491d91ebf.PNG</url>
      <title>DEV Community: Eládio Tchiinhemba</title>
      <link>https://dev.to/tchiinhemba</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tchiinhemba"/>
    <language>en</language>
    <item>
      <title>#1 | Web Services</title>
      <dc:creator>Eládio Tchiinhemba</dc:creator>
      <pubDate>Tue, 09 Jan 2024 09:54:27 +0000</pubDate>
      <link>https://dev.to/tchiinhemba/1-web-services-227b</link>
      <guid>https://dev.to/tchiinhemba/1-web-services-227b</guid>
      <description>&lt;p&gt;Today, let's discuss a bit about Web Services.&lt;/p&gt;

&lt;p&gt;It's common for us to forget things over time, so today, let's revisit something that many may no longer recall.&lt;/p&gt;

&lt;p&gt;Talking about Web Services, means realizing that they are nothing more and nothing less than solutions for applications to communicate with each other, in other words, for one application to talk to another, regardless of language, software, or hardware (regardless of the platform).&lt;/p&gt;

&lt;p&gt;Initially, Web Services were created for message exchange using the XML (Extensible Markup Language) over the HTTP protocol, identified by a URI (Uniform Resource Identifier).&lt;/p&gt;

&lt;p&gt;In summary, we can say that:&lt;/p&gt;

&lt;p&gt;Web Services are APIs that communicate over networks using the HTTP protocol.&lt;/p&gt;

&lt;p&gt;Note: Every Web Service is an API, but not every API is a Web Service.&lt;/p&gt;

&lt;p&gt;APIs can run on different protocols, but Web Services run only on the HTTP protocol.&lt;/p&gt;

&lt;p&gt;In this case, a Web Service ends up being an API that runs on the web.&lt;/p&gt;

&lt;p&gt;URI: It's almost the same as a URL.&lt;/p&gt;

&lt;h2&gt;
  
  
  Advantages
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Common Language
&lt;/h3&gt;

&lt;p&gt;Due to the existence of many programming languages nowadays, making two different systems communicate is challenging. However, you can use a common language between both involved applications, such as JSON or XML.&lt;/p&gt;

&lt;h3&gt;
  
  
  Integration
&lt;/h3&gt;

&lt;p&gt;Since both applications have a common language for information exchange, new integrations become easier.&lt;/p&gt;

&lt;h3&gt;
  
  
  Implementation Reusability
&lt;/h3&gt;

&lt;p&gt;As the output is always the same, reusing this implementation becomes much easier.&lt;/p&gt;

&lt;h3&gt;
  
  
  Security
&lt;/h3&gt;

&lt;p&gt;The Web Service takes care of everything; the rest remains in the intranet, and only the Web Service has access to the database.&lt;/p&gt;

&lt;h3&gt;
  
  
  Costs
&lt;/h3&gt;

&lt;p&gt;In terms of cost, integrating becomes more affordable, especially if you have a Web Service. With it, you don't need to create new solutions for clients who want to access your data.&lt;/p&gt;

&lt;h3&gt;
  
  
  Key Technologies
&lt;/h3&gt;

&lt;p&gt;Architectures used in Web Services!&lt;br&gt;
SOAP&lt;br&gt;
It is more related to XML and will always be used with it.&lt;/p&gt;

&lt;h3&gt;
  
  
  REST
&lt;/h3&gt;

&lt;p&gt;It can be related to XML or JSON, as well as other markup languages.&lt;/p&gt;

&lt;p&gt;About the Subject: Please make sure to share your perspective in the comments! This way, we become more consistent. And if this content is somehow conveying a wrong idea, feel free to correct it. It will be very helpful for me and the community.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
