<?xml version="1.0" encoding="utf-8"?>
<!-- generator="Kirby" -->
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">

  <channel>
    <title>Tag: api-based solution &#183; Blog &#183; Liip</title>
    <link>https://www.liip.ch/en/blog/tags/api-based+solution</link>
    <generator>Kirby</generator>
    <lastBuildDate>Mon, 21 Nov 2016 00:00:00 +0100</lastBuildDate>
    <atom:link href="https://www.liip.ch" rel="self" type="application/rss+xml" />

        <description>Liip blog articles tagged &#8220;api-based solution&#8221;</description>
    
        <language>en</language>
    
        <item>
      <title>How to reduce your development and maintenance costs with APIs?</title>
      <link>https://www.liip.ch/en/blog/industrial-apps-api</link>
      <guid>https://www.liip.ch/en/blog/industrial-apps-api</guid>
      <pubDate>Mon, 21 Nov 2016 00:00:00 +0100</pubDate>
      <description><![CDATA[<p><em>An API-based solution has many advantages. The biggest one is the significant spare on development and maintenance costs, thanks to a modular infrastructure. With the example of a recent work for a watch manufacturer, this blog post explains you in 4 points what added value an API can bring to your IT environment.</em></p>
<h2>Context: a manufacturer's production line without a central server</h2>
<p>We were recently involved in the digital transformation of a manufacturer's production line. The main issue of this manufacturer was control-desktops that were not centrally managed. In consequence, for each code change, an update was required on each control-desktop. It was an expensive and time-consuming process.</p>
<figure><img src="https://liip.rokka.io/www_inarticle/4d57b5160f77b16963165bff92bebe4526e86e04/160829-company-update-a-1024x732.jpg" alt="Production line - A"></figure>
<p>This image represents a production line with standalone control-desktops, and their costly maintenance routines.</p>
<p>We evaluated the potential and feasibility of centralizing the core processes into one single central server. This server codebase would be accessible via an API by the decentralized control-desktops.</p>
<p>The proposed architecture was a web-based solution. This means that each remote unit would access the main server via its web browser (i.e. Google Chrome, Firefox, Internet Explorer, etc.), as you would access any website.</p>
<h2>Your advantages with an API-based solution</h2>
<h3>1/ Up-to-date information at any time</h3>
<p>Linking your server and a web application with an API allows you to control information at any time. In other words, one code deployment on the centralized server updates each control-desktop automatically, because each machine accesses the software via the web browser.</p>
<p>As a result, the data managed in a single location is always up-to-date, and is available through an API to all consuming devices.</p>
<h3>2/ Faster and more flexible deployments</h3>
<p>A central server contains all the codebase. Each control-desktops interacts with the central server. Thus, deploying a new control-desktop is a breeze! There is no more software to setup on each new device: just plug and play.</p>
<h3>3/ Development time reduced — investment lowered</h3>
<p>Operating System versions of the production line have less and less importance thanks to the generalization of web-based softwares. Going through the web browser allows to bypass historical technical constraints such as software and version compatibility, and it's especially relevant since <a href="https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support">Microsoft ended its support for old Internet Explorer versions</a> which were often a source of abnormal bugs.</p>
<p>This means that you do not need to find an “old-technology specialist” anymore. As a consequence, development and maintenance investments get reduced.</p>
<h3>4/ Security increased</h3>
<p>With an API-based infrastructure, process execution happens on one single machine (i.e. the server) instead of X error prone control-desktops. Therefore, this prevents the risk to have old code on the machines, or operating systems not updated to the latest version.</p>
<p>You may wonder if the data transmission security isn't compromised then? This questioning isn't relevant anymore: using tools such as HTTPS/SSL encryption or private networks make this argument invalid.</p>
<h2>To conclude – an easier step to digital transformation</h2>
<figure><img src="https://liip.rokka.io/www_inarticle/dda25c99b6c6456cfcb7be86baae2880689c1494/160829-company-update-b-1024x732.jpg" alt="Production line with API"></figure>
<p>This image represents a production line with a central API server that allows to have always-up-to-date control-desktops' web application.</p>
<p>As explained in this blog post, taking the leap to an efficient and evolutive infrastructure is easier if your software solution is build around APIs. Indeed, an API-based solution will lower your development and maintenance costs, while it will increases your software security.</p>
<p>At Liip, this is how we see industries properly embracing a digital transformation to keep up with their competitors.</p>]]></description>
                  <enclosure url="http://liip.rokka.io/www_card_2/ad03e010a6032b7e471de8a810358fcbe87bc858/160829-company-update-b.jpg" length="103728" type="image/png" />
          </item>
    
  </channel>
</rss>
