Designing Great REST API is important to have great microservices. Code First approach focuses on generating the contract from code. Is it the best possible approach?
You will learn
- What is Code First approach of designing REST API?
- What are advantages of Code First approach?
- What are disadvantages of Code First approach?
- When do you adopt Code First approach?
Free Courses - Learn in 10 Steps
- FREE 5 DAY CHALLENGE - Learn Spring and Spring Boot
- Learn Spring Boot in 10 Steps
- Learn Docker in 10 Steps
- Learn Kubernetes in 10 Steps
- Learn AWS in 10 Steps
This is the fourth article in a series of articles on REST APIs:
- 1 - Introduction to REST API - RESTful Web Services
- 2 - REST v SOAP - A few perspectives
- 3 - Designing REST API - What is Contract First?
- 4 - Designing REST API - What is Code First Approach?
- 5 - REST API - What is HATEOAS?
- 6 - REST API Best Practices - With Design Examples from Java and Spring Web Services
What Is Code First?
Whenever you develop service, such as a REST API or a SOAP API, there are two approaches you could choose from:
- Code First, and generate the contract out of the code
- Contract First, and develop the code based on the contract
Let’s start with a quick example for Code First
Spring Boot Code First REST API Example
We are developing a RESTful web service, by making use of the Spring Boot Framework to generate the API. For example, in the
retrieveAllUsers() API, we expose the
"/users" URI and return all the user resources by calling a service method. when we hit this URL, we get these users returned:
In a similar manner, there are other service methods defied, each with their own URI. What we are doing with this example is taking the code, and generating documentation from it. That documentation lists out how a user can use the service. For this, we use a documentation format called Swagger:
Swagger enables us to generate documentation from the code. For example, the following is what Swagger generates for a request to retrieve all users:
It lists out the kind of response message we get, and the response status accompanying it as well. You can even call that service from Swagger, leading to:
You can also send a POST request to
Swagger tells us how to structure the request message, and specify the individual field formats inside. It will also tell you the type of response you get back, along with the response code.
What Swagger generates out of the code, is called a contract.
Advantages Of Code First
The advantages of this approach are mainly:
- Low-effort contracts: Generating the contract does not require any additional effort. It is just a by-product of the service development, as it can be automatically generated from the code
- Contract, code in-sync: As the contract is generated from the code, the two always in sync with each other
Disadvantages Of Code-First
The disadvantages of this approach are as follows:
No Parallel Development
The service producer and the service consumers cannot be developed in parallel. First the service needs to be developed, then the contract is generated, and only after that, consumer code can be written to adhere to the contract. Without understanding the contract, a consumer cannot be developed.
No Target For Teams
As the contract cannot be known before the service is developed, there is no target for the various stakeholders in development. Hence, there is every chance that directions go wayward, and unnecessary changes are made, leading to wastage of effort.
No Cross-Platform Compatibility
In some older frameworks, it is not that easy to generate the contract from the code. As a result, it is quite common for the contracts generated not being compatible across platforms.
Do check out our video on this:
In this article, we explored the code first approach of building REST API. While code first approach is efficient from a developer perspective, it has significant challenges when it comes to developing the service provider and consumer together.