API - Let's make it simple

-



So, explain to me, what is an API? 

(It's a question I like to ask in an interview once I hear that the candidate has worked with one in his previous role).
Quite surprisingly, not many people can clearly explain this concept in simple words, and I'm not surprised.
If we search for the definition of API online, this is what we will find:
"In computer programming, an application programming interface (API) is a set of subroutine definitions, communication protocols, and tools for building software. In general terms, it is a set of clearly defined methods of communication among various components. A good API makes it easier to develop a computer program by providing all the building blocks, which are then put together by the programmer."

 Now, let's try to break down and better understand this concept.
We live in a world that thrives of connectivity. At the edge of our fingertips, (and on the other side of our screen) there is a whole world that allows us to shop, post, search and enjoy a wide range of content from anywhere in the world. But let's think about it, how does Data get from point A to point B?
API - stands for "Application programming interface" - It is an "Under the hood mechanism" what makes it possible for numerous interactions we perform with different applications and services.
Some time ago, I saw this great analogy on Twitter that really makes it simple for people to understand what is really an API.

Imagine that you are sitting in a restaurant, in front of you there is a menu. In order for you to receive anything from the kitchen, you need to state your order to the waiter, and it has to exist on the menu.
Once you place your order the waiter will go to the kitchen, and return to you with your food.

In other words...
You are the client, the waiter is the API, and your order in an API call which the restaurant exposed to you so you could use it to retrieve items from the kitchen which is the server. The API in the critical link which allows us to receive responses what the desired service.



 In real life...
Think about an online shopping website that searches and aggregates results from various different online stores. The website interacts with the stores via the API they expose so he could provide you with the response. Just like asking your waiter, you are making a search on the website, the website communicates an API call to the store's interface, and "retrieves" the response back to the website which displays it to you.
The same principle applies to various interactions between applications, devices and Data.
I hope this simple and short explanation made it easier for you to understand the concept of API and it's place in our everyday activities. Read, explore and never stop learning.

Credit to Aarthi Dee on Twitter.



קורס אוטומציה למתקדמים - ההרשמה נפתחה למחזור ספטמבר
:פרטים בלינק

Comments

Post a Comment

Popular posts from this blog

Sharing is caring - Intro to Jenkins shared libraries

-
Image
  Whether you're just dipping your toes into the world of automation infrastructure, or already crafting your first jobs to automate your test execution, Jenkins is your new best friend.  In this blog post, we will talk a bit more about the practice of infrastructure as code, its relevance to test automation, and how you can avoid code duplications, align with industry best practices, and enable velocity, maintainability, and collaboration. So, whether you're a seasoned pro or just starting out, let's dive into the world of Jenkins Shared Libraries and see how they can make your life easier. Jenkins Shared Libraries play a crucial role in the realm of Infrastructure as Code (IaC).  So, what are they exactly? Think of Jenkins Shared Libraries as your secret stash of code snippets, neatly organized and ready to be plugged into your pipelines whenever needed. Let's explore the aspect of reusability within Jenkins Shared Libraries: Reusability is the cornerstone of efficien
Read more

Intro to Terraform and how it is related to test automation infrastructure

-
Image
In this post, we will take a closer look at one of the most popular infrastructure-as-code software tools developed by HashiCorp, and if you follow my recent content, that name should start ringing a few bells. So, what is Terraform and why do we need it? Terraform allows you to define and describe your infrastructure in the form of code. To be more specific “HashiCorp declarative configuration language” (or HCL in short). With Terraform you can manage your resources and infrastructure modules like servers, VPCs, security groups, and much more, even if they are located on different providers such as AWS or Azure.  Generally speaking, cloud providers have their own infrastructure-as-code tools like CloudFormation or ARM. But, Terraform has very extensive support for different cloud providers and platforms allowing you to use a single tool for cross-cloud configurations. This makes it easier to manage your resources, easier to onboard and this is a scalable and in general, the “best prac
Read more

Chromedriver - Under The Hood

-
Image
Selenium Webdriver has been our companion in our test automation adventures for some time now. Over the years the Selenium open source project has obtained something I can fairly describe as global domination. With Selenium, we are able to interact with different browsers using the WebDrivers. But, how much do we really know about them and the way they work? In this article, we will take a closer look into "Chromedriver" and explore a little bit about how it works. So, what is the role of this Webdriver? Starting from the release of Selenium 2, we were introduced to the concept of Webdriver. The "Chromedriver" for example is a .exe file that is able to act as a server. His role is to allow us to "Interact" with the browsers. Eventually, the responsibility for developing and maintaining these drivers was transferred to the browser vendors. The idea is, that they know their browsers the best and the produces driver would be much more stable and
Read more