API development practices

: This article mainly introduces API development practices. if you are interested in the PHP Tutorial, you can refer to it. In 2015, if you want to add a label to yourself, it should be an API.

Customizes various API frameworks in different systems.

• In the development of APIs for connecting malls to various e-commerce ERP systems, I used SHOPEX-compatible API interfaces, because various ERP systems are basically supported.
• In the development of Zen-Tao API interfaces, I compared the support of mainstream IDE interfaces for Issue management systems on the market, and used the Redmine API compatibility mode for development.
• And so on.

In API Design, one of the most interesting ones should be compatible. Although Oracle won the Java API lawsuit, API compatibility is undoubtedly a matter of self-interest.

You don't need to talk about the advantages!

Remember an advertisement: world, China, China, world!

Compatibility with analogy interfaces: others' interfaces, yours; your interfaces, others!

I don't want to talk about the details of API design here, because if I design it independently, radish and vegetables will often have their own love and diverse forms and styles.

However, once compatible, although the API's initial initiator will receive explicit or implicit benefits, it is undoubtedly a "good news" for the end users of the API ". Of course, from the perspective of Linux community culture, it is unacceptable. The world should be colorful!

The rest api design style is indeed concise everywhere, but most people have not realized the necessity of applying this style.

In any case, Web programmers will inevitably switch from full-stack development thinking to API design thinking.

The above introduces the API development practices, including some content, and hopes to help those who are interested in the PHP Tutorial.