Home > Article > Backend Development > PHP Best Practices (Translated) - A Practical Guide to PHP's Confusing Technologies_PHP Tutorial
-------------------------------------------------- -------------------------------------------------- ------------------
PHP is a complex language that has been tweaked over the years to make its different versions highly inconsistent and sometimes buggy. Each version has its own unique features, redundancies, and quirks, and it can be difficult to keep track of which version has which issues. It's easy to understand why it sometimes gets so much hate.
Despite this, today it is the most popular language for web development. Because of its long history, you can find many tutorials for implementing basic tasks such as password hashing and database access. But the problem is that after 5 tutorials, you are likely to find 5 completely different ways to complete the task, so which one is the "correct" way? Are there elusive bugs or pitfalls in other ways? It's really hard to figure out, so you often have to look it up on the internet to try and get the right answer.
This is one of the reasons why newbies to PHP programming are so frequently blamed for ugly, outdated, or unsafe code. If the first result of a Google search is a 4-year-old article describing a 5-year-old method, it will be difficult for new PHP users to change the status quo that they are often blamed for.
This document attempts to solve the above problems by organizing a series of basic practices considered best practices for common confusing problems and tasks in PHP. If a low-level task has multiple confusing ways to implement it in PHP, this article will also cover it.
What is it
This is a guide that suggests best practices for PHP programmers when they encounter some common low-level tasks but don't know the best practices (since PHP may provide multiple solutions). For example: Connecting to a database is a common task, and PHP provides a lot of possible solutions, but not all of them are good practices, so this article will also cover this issue.
This article contains a series of short, introductory solutions. The examples involved will work with basic settings, and you should be able to turn them into something useful for you by playing around with them.
This article will point out some of what we consider to be the latest and greatest in PHP. However, this means that if you are using an older version of PHP, some of the features used to implement these solutions will not be available to you.
This document will be updated all the time, and I will do my best to keep this document up to date with the development of PHP.
Nothing
This document is not a PHP tutorial. You should learn language basics and grammar elsewhere.
Nor is it a guide to common web application issues such as cookie storage, caching, programming style, documentation, etc.
It is also not a safety guide. While this document touches on some security-related issues, I also hope that you will do your own research to ensure the security of your PHP applications. Any problems caused by your code should be your own fault.
This document does not advocate a specific programming style, pattern, or framework.
It is not advocating a specific way to complete high-level tasks such as user registration, logging into the system, etc. This documentation is limited to some low-level tasks that are confusing or unclear due to PHP's long history.
It is not a one-and-done solution, nor is it the only solution. Some of the methods described below may not be the best for your specific scenario. There are many different ways to achieve the same goal. In particular, high-load web applications may benefit more from more complex solutions.