Implementing Endpoints
Start course

In this course, we will learn the concepts of microservice and spring framework with a focus on Domain-Driven Design.

Learning Objectives

  • Domain-Driven Design

Intended Audience

  • Beginner Java developers
  • Java developers interested in learning how to Build and Deploy RESTful Web Services
  • Java Developers who want to develop web applications using the Spring framework
  • Java Developers who want to develop web applications with microservices
  • Java Developers who wish to develop Spring Boot Microservices with Spring Cloud


  • Basic Java knowledge

Hello there. In this video, we will talk about the endpoints. We already used them in the projects we did in our course. But in this video, I will give brief information about the endpoint. So, if you're ready, let's begin. First, I want to talk about APIs. An Application Programming Interface or API allows two systems to communicate with each other. An API essentially provides the language and contract for how two systems interact. Each API has documentation and specifications that determine how information can be transferred. Just like a web page is rendered, APIs can use HTTP requests to get information from a web application or web server. APIs are typically categorized as either SOAP or REST and both are used to access web services. SOAP relies solely on XML to provide messaging services, while REST offers a more lightweight method using URLs in most cases to receive or send information. REST uses four different HTTP 1.1 verbs: GET, POST, PUT, and DELETE to perform tasks.

Unlike SOAP, REST doesn't have to use XML to provide the response. You can find REST-based web services that output the data in Command Separated Value, CSV, JavaScript Object Notification, JSON, and Really Simple Syndication, RSS. The point is that you can obtain the output you need in a form that's easy to parse within the language you need for your application. After providing a brief overview of APIs, it's time to discuss endpoints. Simply put, an endpoint is one end of a communication channel. When an API interacts with another system, the touchpoints of this communication are considered endpoints. For APIs, an endpoint can include the URL of a server or service. Each endpoint is location from which APIs can access the resources they need to carry out their functions. APIs work using requests and responses. When an API request information from a web application or web server, it will receive response. The place where API send requests and where the resource lives is called an endpoint.

All over the world, companies leverage APIs to transfer vital information, processes, transactions and more, making sure that each touchpoint in API communication is intact, is vital to the success of each API. Endpoints specify where resources can be accessed by APIs and play a key role in guaranteeing the correct functioning of the software that interacts with them. In short, API performance relies on its ability to communicate effectively with API endpoints. All right, so I think that's enough information about endpoints. Let's take a short break here and I'll see you in the next video.


About the Author
Learning Paths

OAK Academy is made up of tech experts who have been in the sector for years and years and are deeply rooted in the tech world. They specialize in critical areas like cybersecurity, coding, IT, game development, app monetization, and mobile development.