Series
Article Series
Here you'll find related articles organized by topic, making it easier for you to read systematically.
Why Hotel API Integration Is So Hard
An in-depth exploration of various challenges in hotel API integration, from authentication to protocol differences, from error handling to performance optimization.
-
5 suppliers, 5 different authentication methods—Basic Auth, HMAC-SHA256, OAuth1, JWT...
-
Besides different authentication methods, API protocols are also diverse...
-
The same field may have completely different meanings across different supplier APIs...
-
Part 4 Why Hotel API Integration Is So Hard (4): Error Handling - Same Error, 5 Different Status Codes
Supplier error codes are inconsistent, and HTTP status codes are often misused...
-
Each supplier has different rate limiting policies, requiring careful design...
-
Hotel data changes at different rates, requiring intelligent caching strategies...
-
Reviewing entire API integration process and summarizing best practices...
AI Coding Practice
From DeepSeek to Claude Code, exploring practice and experience of AI-assisted programming.
-
We experimented with various AI coding tools in HotelByte project...
-
How to switch from DeepSeek to Claude Code while maintaining code quality...
-
Integrating Claude Code into our development workflow...
-
Using multiple AI models simultaneously to leverage their strengths...
-
Using OpenSpec specifications to drive AI-assisted development...
-
Summarizing best practices and considerations for AI coding...
HTTP Dispatcher
Deep dive into design and implementation of HTTP Dispatcher.
-
Introducing concept and role of HTTP Dispatcher...
-
How to implement efficient rate limiting and connection pool management...
-
Implementing HTTP Dispatcher using Go language...
Supplier Proxy
Design and implementation of supplier proxy.
-
Introducing concept and role of Supplier Proxy...
-
How to handle authentication and errors in Supplier Proxy...
Comments