Guy Levin

CTO at RestCase

Netanya, IL

Joined Dec 2015

https://www.restcase.com

About

GUY LEVIN (@RestCaseApi) is the CTO of RestCase, a company that develops REST API Development Platform in order to help companies and developers speed up development of RESTful services and minimalize time-to-market. Guy is an architect focusing on distributed and cloud systems, full stack software engineer and a DBA. He has over 20 years’ experience of software development in a variety of sectors including medical and healthcare, cyber security, fintech and more. In his free time Guy is experimenting with new technologies, building websites, mobile applications and a blog writer.

Stats

Reputation:	1348
Pageviews:	998.2K
Articles:	12
Comments:	3

Articles
Comments

Articles

7 Rules for REST API URI Design

These seven simple rules will help you write readable, conflict-free URIs that communicate all necessary resource information.

Updated October 27, 2023

· 80,298 Views · 30 Likes

Top 5 REST API Design Problems

In this article, look at five REST API design problems, such as using body in GET requests, the usage of wrong or lengthy parameter names, and more.

December 4, 2019

· 55,793 Views · 14 Likes

Four Most Used REST API Authentication Methods

Get the four most used REST API authentication methods.

Updated August 6, 2019

· 130,517 Views · 15 Likes

Top 7 REST API Security Threats

Look at the top 7 REST API security threats in today’s IT world in order to become aware of security threats.

January 10, 2019

· 29,679 Views · 10 Likes

The Role of API Gateways in API Security

Let's take a look at the role of API gateways in API security as well as explore the advantages, drawbacks, and opportunities and vulnerabilities.

August 29, 2018

· 53,560 Views · 22 Likes

REST API Error Handling — Problem Details Response

I wish that I knew then what I know now about rfc7807, the standard that actually defines the interface of a correct and well-known error response.

June 21, 2018

· 76,790 Views · 14 Likes

Benefits of REST APIs With HTTP/2

HTTP/2 brings with it a lot of benefits for REST APIs, both on the integration side of things and in terms of performance and security.

January 9, 2018

· 73,672 Views · 83 Likes

Internal vs. External APIs

The key to dealing with data is to figure out which audience is appropriate for each data set, and then open up that data to the correct audience via APIs.

March 29, 2017

· 19,182 Views · 6 Likes

Top 5 REST API Security Guidelines

Here is an annotated list of security guidelines for your REST APIs when you are developing and testing them, including proper authorization, input validation, and output encoding.

December 21, 2016

· 145,165 Views · 47 Likes

An API-First Development Approach

The API-first approach allows products to evolve into organic, self-organizing ecosystems that can grow to handle new and unforeseen demands.

November 15, 2016

· 71,671 Views · 5 Likes

5 Basic REST API Design Guidelines

These guidelines from Guy Levin are intended to help you in creating clean, easy to use, and easily understandable APIs.

October 4, 2016

· 62,225 Views · 60 Likes

REST API vs. SOAP Web Services Management

Let's take a step back and look at the rise of microservices and REST and the apparent decline of SOAP-based web services. What are the statistics and the reasons?

August 4, 2016

· 13,402 Views · 9 Likes

Comments

The Role of API Gateways in API Security

Sep 07, 2018 · Lauren Forbes

Hi,

Sorry, I meant Mark Cheshire, chief operating officer of San Francisco-based API gateway vendor 3scale Inc.

Thanks,

Guy

Benefits of REST APIs With HTTP/2

Jan 17, 2018 · Jordan Baker

I think that multiplexing is allowing the client to request several resources at once. Currently, this is possible when the browser is requesting a resource from different sources (like CDN's and etc..). But if you are requesting for example "styles.css" and "scripts.js" from the same location (let's say localhost), it will be requested by the client one by one, opening a connection for each and every resource. In HTTP/2 the client can request several resources at once, they are also will be served faster as it is not synchronous calls anymore. The connection that is always open also contributes to the request \ response times in terms of the time used to open and close a connection is not wasted.

7 Rules for REST API URI Design

Jul 11, 2017 · Arran Glen

I would not use GET in any case.

I think you can use:

DELETE http://<api>/students

but with additional header indicating some sort of confirmation.