Skip to main content

Go #6 - REST Api with Go using net/http

net/http:

This is available out of the box in Go language. Package "net/http" provides HTTP client and server implementations which can be used to make common HTTP requests like GET, POST, PUT, DELETE e.t.c..

While building REST Api's with Go using net/http, here are few methods and interfaces we should understand:

type Handler 
type Handler interface {
    ServeHTTP(ResponseWriter, *Request)
}

- A Handler is responsible for responding to HTTP requests. This interface has only one method ServeHTTP(ResponserWriter, *Request)
- You can define your own struct as a Handler which implements ServeHTTP method with ResponseWriter and pointer to Request as arguments 
package main

import (
    "net/http"
)

type server struct{}

func (s *server) ServeHTTP(writer http.ResponseWriter, req *http.Request) {
    writer.Header().Set("Content-Type", "application/json")
    writer.WriteHeader(http.StatusOK)
    writer.Write([]byte(`{"message": "Go world"}`))
}


func main() {
    s := &server{}
    http.Handle("/", s)
    http.ListenAndServe(":9780", nil)
}

ListenAndServe
func ListenAndServe(addr string, handler Handler) error
- Starts an HTTP server to serve the requests with a given address and handler

Handle
func Handle(pattern string, handler Handler)
- Handle registers the handler for given pattern in DefaultServeMux
- ServeMux matches the URL of each incoming request against a list of registered patterns and calls the handler for the pattern that most closely matches the URL. In our main(), we can see passing our own handler for the given pattern

HandleFunc
func HandleFunc(pattern string, handler func(ResponseWriter, *Request))
- HandlerFunc registers the handler function for the given pattern in DefaultServerMux
- The problem with Handle is you have to write an empty struct and implement ServeHTTP your struct does nothing other than that, so to eliminate that dumb struct and simplify your code you can use HandleFunc
- Above code can be refactored as below, notice that we removed struct and ServeHTTP instead defined a new handler function and registered it
func helloGo(writer http.ResponseWriter, req *http.Request) {
    writer.Header().Set("Content-Type", "application/json")
    writer.WriteHeader(http.StatusOK)
    writer.Write([]byte(`{"message": "Go world"}`))
}

func main() {
    http.HandleFunc("/", helloGo)
    http.ListenAndServe(":9780", nil)
}

Though net/http is a great package for our REST api needs. It comes with few limitations like only two keep-alive connections, not easy to handle path/ query params e.t.c.. you can read more about limitations here so to solve some of these problems most real world applications use gorilla mux or gin-gonic. I'll try to cover them both in my future posts.

Happy Coding 🤖

Comments

Popular posts from this blog

Spring Boot - RestTemplate PATCH request fix

  In Spring Boot, you make a simple http request as below: 1. Define RestTemplate bean @Bean public RestTemplate restTemplate () { return new RestTemplate (); } 2. Autowire RestTemplate wherever you need to make Http calls @Autowire private RestTemplate restTemplate ; 3. Use auto-wired RestTemplate to make the Http call restTemplate . exchange ( "http://localhost:8080/users" , HttpMethod . POST , httpEntity , String . class ); Above setup works fine for all Http calls except PATCH. The following exception occurs if you try to make a PATCH request as above Exception: I / O error on PATCH request for \ "http://localhost:8080/users\" : Invalid HTTP method: PATCH ; nested exception is java . net . ProtocolException : Invalid HTTP method: PATCH Cause: Above exception happens because of the HttpURLConnection used by default in Spring Boot RestTemplate which is provided by the standard JDK HTTP library. More on this at this  bug Fix: This can b...

RADUS#4 - Caching the response in REST API's

  Caching in spring boot app: Caching can be used to provide a performance boost to your application users by avoiding the business logic processing involved again and again, load on your DB, requests to external systems if the users request data that's not changed frequently Different types of caching: We'll be focusing more on in-memory caching in this post i listed other options available to have an idea. In-memory caching You'll have a key-value data stores that stores the response of the request after it is served for the first time There are multiple systems like Redis, Memcached that do this distributed caching very well By default Spring provides concurrent hashmap as default cache, but you can override CacheManager to register external cache providers. Database caching Web server caching Dependencies needed: Maven < dependency > < groupId > org . springframework . boot </ groupId > < artifactId > spring - boot - starter - cache ...

Settings.xml for Maven, JFrog

For development and deployment of applications we always use an artifactory in real-time world to host artifacts needed for your build and also as a target to deploy artifacts generated in the build process. For Maven, to communicate with artifactory we need a settings.xml file which is usually located at "/User/rake/.m2/settings.xml" this file consists of how to authenticate to the artifactory servers and authorizations to read/ write to different locations like release, snapshots e.t.c... Settings.xml can be generated using the artifactory you're using which in my case is JFrog , but here's a sample settings file for your reference incase you're feeling lazy☺ <?xml version="1.0" encoding="UTF-8"?> <settings xsi:schemaLocation= "http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd" xmlns= "http://maven.apache.org/SETTINGS/1.1.0" xmlns:xsi= "http://www.w3.org/2001/XM...