Project

General

Profile

Actions

Task #486

open

Task #482: BackEnd common concepts investigation

BackEnd common concepts investigation[Vĩ]

Added by Tuan Vi Mang about 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Start date:
10/25/2023
Due date:
10/25/2023 (over 2 years late)
% Done:

100%

Estimated time:
1:00 h

Description

1. API (Application Programming Interface):
• An API is a set of rules and protocols that allows one software application to interact with another. It defines the methods and data formats that applications can use to request and exchange information.
• APIs are used for various purposes, such as enabling communication between different software components, services, or systems. They are essential for building applications that rely on data or functionality provided by other services or platforms. APIs enable integration, automation, and the exchange of data between different applications.
2. Swagger:
• Swagger is a framework for documenting, designing, and testing APIs. It provides a user-friendly interface for developers to document their APIs in a standardized way. Swagger allows API developers to describe the endpoints, request/response parameters, and authentication methods of their APIs in a machine-readable format (usually YAML or JSON).
• Swagger documentation can be used to generate interactive API documentation, making it easier for developers to understand and use the API. It also helps in automated code generation and testing.
3. CRUD (Create, Read, Update, Delete):
• CRUD is an acronym that represents the four basic operations for managing data in a database or application:
• Create: Create new records or objects.
• Read: Retrieve data from the database.
• Update: Modify existing data or records.
• Delete: Remove data or records from the database.
• CRUD operations are fundamental for any application that interacts with a database or needs to manage data. They correspond to the basic actions you can perform on most data-driven applications.
4. Relationship between Frontend, Backend, and Database:
• In a typical software application architecture:
• Frontend: This is the user interface or the client-side of the application. It's what users interact with. It includes web pages, mobile app screens, or any interface that users see and interact with. It communicates with the backend to request and display data.
• Backend: This is the server-side of the application. It handles requests from the frontend, processes data, and interacts with the database. It contains the application's business logic and serves as an intermediary between the frontend and the database.
• Database: This is where data is stored and managed. It can be a relational database (e.g., PostgreSQL, MySQL), a NoSQL database (e.g., MongoDB), or any data storage system. The backend communicates with the database to read, write, and manage data.
• The frontend communicates with the backend using APIs to request and send data. The backend processes these requests and interacts with the database to perform CRUD operations or retrieve data. This separation of concerns between the frontend, backend, and database is a common architectural pattern in software development.
5. More Related Information:
• APIs are used extensively in web development, mobile app development, and integration of third-party services.
• RESTful APIs (Representational State Transfer) are a common type of API architecture that follows certain principles for designing networked applications.
• GraphQL is an alternative to RESTful APIs, offering more flexibility and efficiency in data retrieval.
• API security is crucial, and techniques like OAuth and API keys are used to protect APIs from unauthorized access.
• API versioning is often used to manage changes and updates to APIs while maintaining backward compatibility for existing clients.
• API testing tools like Postman and Swagger are used to ensure that APIs work as expected.
• Microservices architecture relies heavily on APIs for communication between individual services

No data to display

Actions

Also available in: Atom PDF