NEW BOT Телеграм, страница

47 views10:21

Forwarded from Linuxor ?

این تیتر هم جالب بود 9 الگورتیمی که بر دنیای ما حکمرانی می‌کنند.

@Linuxor

42 views10:24

Forwarded from Webinarfarsi | Soheib Kiani | وبینار فارسی

کامل ترین “Cheat Sheet” موجود برای Rest API ! ! !
تقریبا بیشتر مواردی که اینجا مطرح هستش بهش اشاره شده

با سرچ کردن keyword ها میتونید به اطلاعات خوبی برسید

Architectural Principles of REST

1. Client-Server Architecture
- Strict separation of concerns
- Clients make requests
- Servers process and respond
- Enables independent evolution of components

2. Statelessness
- Each request contains complete context
- No server-side session storage
- Improves scalability and reliability
- Enables horizontal scaling

3. Cacheability
- Responses can be cached
- Reduces server load
- Improves response times
- Clearly defined cache control mechanisms

4. Layered System
- Components can be independently replaced
- No direct dependency between layers
- Enhances system flexibility
- Supports complex architectures

5. Uniform Interface
- Standardized communication protocol
- Consistent resource identification
- Manipulation through representations
- Self-denoscriptive messages

HTTP Methods Detailed

GET
- Purpose: Retrieve resource data
- Characteristics:
- Safe operation
- Idempotent
- No side effects
- Example: /users/123

POST
- Purpose: Create new resources
- Characteristics:
- Submits data to server
- Generates new resource
- Not idempotent
- Example: /users

PUT
- Purpose: Complete resource replacement
- Characteristics:
- Updates entire resource
- Idempotent
- Requires full resource representation
- Example: /users/123

PATCH
- Purpose: Partial resource modification
- Characteristics:
- Updates specific fields
- More efficient than PUT
- Less bandwidth consumption
- Example: /users/123

DELETE
- Purpose: Remove resources
- Characteristics:
- Removes specified resource
- Idempotent
- Can return success/failure status
- Example: /users/123

HTTP Status Codes

2xx Success
- 200 OK: Standard successful response
- 201 Created: Resource successfully generated
- 204 No Content: Successful request with no response body

3xx Redirection
- 301 Moved Permanently: Resource relocated
- 304 Not Modified: Cached resource unchanged
- 307 Temporary Redirect: Temporary resource movement

4xx Client Errors
- 400 Bad Request: Invalid syntax
- 401 Unauthorized: Authentication required
- 403 Forbidden: Insufficient permissions
- 404 Not Found: Resource doesn't exist
- 409 Conflict: Request conflicts with current state

5xx Server Errors
- 500 Internal Server Error: Unexpected server issue
- 502 Bad Gateway: Invalid server response
- 503 Service Unavailable: Temporary server limitations
- 504 Gateway Timeout: Server didn't receive timely response

Resource Design Principles

Endpoint Naming
- Use nouns
- Prefer plural forms
- Lowercase with hyphens
- Hierarchical and logical structure
- Example: /user-profiles/active

Query Parameters
- Filtering: ?status=active
- Sorting: ?sort=name
- Pagination: ?page=2&limit=50

Security Best Practices

Authentication
- OAuth 2.0
- JWT (JSON Web Tokens)
- API Keys
- OpenID Connect

Authorization
- Role-Based Access Control (RBAC)
- Attribute-Based Access Control (ABAC)
- Fine-grained permission management

Protection Strategies
- Always use HTTPS
- Input validation
- Output encoding
- Rate limiting
- CORS configuration
- Security headers
- Regular security audits

Performance Optimization

Caching Strategies
- Browser caching
- CDN implementation
- ETag support
- Cache-Control headers

Efficiency Techniques
- Compression
- Minimal payload
- Efficient serialization
- Pagination
- Bulk operations

Documentation Guidelines
- Clear endpoint denoscriptions
- Request/response examples
- Error code explanations
- Authentication requirements
- Version management

44 views15:35