How to develop a productive HTTP client in Golang (Go)

How to develop a productive HTTP client in Golang (Go), available at $59.99, has an average rating of 4.75, with 45 lectures, based on 205 reviews, and has 1990 subscribers.

You will learn about Understand the paradigms behind the Go programming language. What an HTTP client is. How to perform HTTP calls in Go. Issues and blocks when working with native HTTP client. How to design a Go library from scratch using Modules. How to design a public API: Interfaces and methods. How to provide mocking features out of the box. Unit, integration and functional testing our HTTP client. Most important: End up with a production-ready HTTP client that you can use without worrying about performance! This course is ideal for individuals who are Software engineers. or Software developers. or QA engineers. or Tech Leads & Architects. It is particularly useful for Software engineers. or Software developers. or QA engineers. or Tech Leads & Architects.

Enroll now: How to develop a productive HTTP client in Golang (Go)

Summary

Title: How to develop a productive HTTP client in Golang (Go)

Price: $59.99

Average Rating: 4.75

Number of Lectures: 45

Number of Published Lectures: 45

Number of Curriculum Items: 45

Number of Published Curriculum Objects: 45

Original Price: $27.99

Quality Status: approved

Status: Live

What You Will Learn

Understand the paradigms behind the Go programming language.

What an HTTP client is.

How to perform HTTP calls in Go.

Issues and blocks when working with native HTTP client.

How to design a Go library from scratch using Modules.

How to design a public API: Interfaces and methods.

How to provide mocking features out of the box.

Unit, integration and functional testing our HTTP client.

Most important: End up with a production-ready HTTP client that you can use without worrying about performance!

Who Should Attend

Software engineers.

Software developers.

QA engineers.

Tech Leads & Architects.

Target Audiences

Software engineers.

Software developers.

QA engineers.

Tech Leads & Architects.

Have you ever called a REST API from your Go program? Did you implemented your own HTTP client or did you ended up using some of the thousand libraries out there? Do you know what your HTTP client is doing in the background?

In this course we’re starting from scratch! We’re going to remember how a basic HTTP call looks like by digging into the request & response objects. We’re going to write a basic HTTP client to perform HTTP requests and then use it in productive applications. What issues do we have? Can we scale our applications by following this approach? Of course not! That’s why we’re creating an HTTP client library that provides:

Fast, reliable and friction-free HTTP connections.

Support for all HTTP methods: GET, POST, PUT, DELETE, PATCH and more!

A Concurrency-Safe HTTP client that you can use without worrying about performance.

Content type management and optimization.

Mocking features out of the box.

A clean interface in case you want to unit test your code without relying on integration testing features.

A robust implementation so you won’t need any external dependency whatsoever.

Completely customizable interface: timeouts, transport layer, custom HTTP client and lots of useful features.

A library that is PRODUCTION-READY!

If you’re looking to integrate a 3rd party REST APIs in your code, you’ll need to perform an HTTP call to it. Make sure you take a look at this course before even considering alternatives out there that will force you to use different dependencies for running, testing and extending your code! As Robert Pike says: “A little copying is much better than a little dependency”. In this course we’re not only getting rid of the dependencies but we’re also getting rid of the copying. We’re not using anything more than the Go’s standard libraryto design & develop our own HTTP client.

This client will the baseline for all of the applications we’re going to build later, making our business scale and grow as fast as we can Go.

Take a look at the preview lessons you have available to have an idea about the structure and content of the course. I know you’re going to enjoy it! If you have any doubt, take a look at my other courses and see what my students have to say!

See you on the other side!

Course Curriculum

Chapter 1: Introduction

Lecture 1: Introduction

Lecture 2: Welcome!

Lecture 3: The reason for this course

Lecture 4: What were going to build

Chapter 2: HTTP calls

Lecture 1: How an HTTP call looks like

Lecture 2: Connections and timeouts

Lecture 3: Implementing a basic HTTP GET

Lecture 4: Default problems

Lecture 5: The reason for a new library

Chapter 3: Working on the core

Lecture 1: Introduction to Go modules

Lecture 2: Go basics: Structs, functions, interfaces and methods.

Lecture 3: Adding basic behavior

Lecture 4: Defining custom & common headers

Lecture 5: Dealing with the request body

Lecture 6: Testing, testing and testing!

Lecture 7: Be careful with code coverage

Lecture 8: Dealing with timeouts

Lecture 9: Allow timeout customization

Lecture 10: Allow timeout disabling

Lecture 11: Builder pattern applied

Lecture 12: Refactoring our builder implementation

Lecture 13: Making the client concurrent-safe

Lecture 14: Using our custom response implementation

Chapter 4: Testing & Mocking features

Lecture 1: Creating our examples

Lecture 2: Should we provide mocking features?

Lecture 3: Defining the Mock struct

Lecture 4: Adding the mock server

Lecture 5: Responding from the mock server

Lecture 6: Adding a default mock

Lecture 7: How to flush every active mock

Lecture 8: Improving mock body and keys

Chapter 5: Publishing & using our library

Lecture 1: How to publish a Go module

Lecture 2: How to use our Go module

Lecture 3: Easily testing API calls with our library

Chapter 6: Tuning our library

Lecture 1: Allowing custom HTTP client

Lecture 2: Clean our public interface

Lecture 3: Adding documentation to our code

Lecture 4: Adding more examples

Lecture 5: Allow user agent definition

Lecture 6: Defining common constants

Lecture 7: Releasing the first stable version!

Lecture 8: Cleaning our mocking interface

Lecture 9: Changing how we mock requests

Lecture 10: Cleaning our mock server

Chapter 7: Final chapter

Lecture 1: What we have done

Instructors

Federico León
Technical Leader

Rating Distribution

1 stars: 2 votes

2 stars: 5 votes

3 stars: 19 votes

4 stars: 49 votes

5 stars: 130 votes

Frequently Asked Questions

How long do I have access to the course materials?

You can view and review the lecture materials indefinitely, like an on-demand channel.

Can I take my courses with me wherever I go?

Definitely! If you have an internet connection, courses on Udemy are available on any device at any time. If you don’t have an internet connection, some instructors also let their students download course lectures. That’s up to the instructor though, so make sure you get on their good side!