


How to distinguish between business logic and non-business logic in back-end development and perform reasonable layered design?
Apr 19, 2025 pm 08:45 PMBack-end hierarchical architecture: clear boundaries between business logic and non-business logic
In back-end development, the common three-tier architectures of controller, service and dao are not always clear enough. This article discusses how to effectively distinguish between business logic and non-business logic in the service and dao layers, and even after introducing the manager layer, so as to build a more reasonable layered design.
Definition between business logic and non-business logic
Business logic directly relates business requirements, while not business logic is responsible for underlying operations, such as data access, data verification, etc. Blurred boundaries between the two often lead to confusion in code.
-
Encapsulation of data operations: For example,
UserManager.delete()
andDepartmentManager.delete()
may handle the associated deletion ofUserDeptModel
at the same time. This is non-business logic because it focuses on data consistency rather than the business process itself. Code example:class UserManager: def delete(self, user_id): self.user_dao.delete(user_id) self.user_dept_dao.delete_by_user_id(user_id) class DepartmentManager: def delete(self, dept_id): self.dept_dao.delete(dept_id) self.user_dept_dao.delete_by_dept_id(dept_id)
-
Data security processing: password salting and other operations are usually performed at dao or manager layer, because this is a data protection mechanism, not business logic. Code example (Python with hypothetical
salt
function):class UserDao: def save(self, user): user.password = self.salt(user.password) # ... save user to database ... def salt(self, password): # ... password salting logic ... return salted_password
DAO layer method naming specification: DAO layer method names should avoid including business meanings. For example,
get_super_user()
is not as clear asget_user_by_type("super")
.External service call encapsulation: If the backend depends on external services, these calls should be encapsulated at the DAO layer, not the service layer, because this is data access, not business logic.
Simulate Django filter function
In Python, if there is no dependency injection framework, mocking Django filter requires processing request parameters at the DAO layer and passing them layer by layer. Java's Spring framework simplifies this process.
Data entity and hierarchy relationship
Controller, service and dao do not correspond one by one. Their responsibilities are as follows:
- Controller: System entry, receive and process requests, keeping it lightweight.
- Service: The core business logic processing layer is relatively complex.
- DAO: The data access layer is only responsible for data interaction and does not include business logic.
For example, "Create User" business: The Service layer performs "check whether the user name is duplicated" and "create user"; the DAO layer provides "query users based on user name" and "save users" methods.
By clearly distinguishing business logic from non-business logic and following a reasonable layered design, the maintainability and scalability of the code can be improved.
The above is the detailed content of How to distinguish between business logic and non-business logic in back-end development and perform reasonable layered design?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

To realize text error correction and syntax optimization with AI, you need to follow the following steps: 1. Select a suitable AI model or API, such as Baidu, Tencent API or open source NLP library; 2. Call the API through PHP's curl or Guzzle and process the return results; 3. Display error correction information in the application and allow users to choose whether to adopt it; 4. Use php-l and PHP_CodeSniffer for syntax detection and code optimization; 5. Continuously collect feedback and update the model or rules to improve the effect. When choosing AIAPI, focus on evaluating accuracy, response speed, price and support for PHP. Code optimization should follow PSR specifications, use cache reasonably, avoid circular queries, review code regularly, and use X

User voice input is captured and sent to the PHP backend through the MediaRecorder API of the front-end JavaScript; 2. PHP saves the audio as a temporary file and calls STTAPI (such as Google or Baidu voice recognition) to convert it into text; 3. PHP sends the text to an AI service (such as OpenAIGPT) to obtain intelligent reply; 4. PHP then calls TTSAPI (such as Baidu or Google voice synthesis) to convert the reply to a voice file; 5. PHP streams the voice file back to the front-end to play, completing interaction. The entire process is dominated by PHP to ensure seamless connection between all links.

When choosing a suitable PHP framework, you need to consider comprehensively according to project needs: Laravel is suitable for rapid development and provides EloquentORM and Blade template engines, which are convenient for database operation and dynamic form rendering; Symfony is more flexible and suitable for complex systems; CodeIgniter is lightweight and suitable for simple applications with high performance requirements. 2. To ensure the accuracy of AI models, we need to start with high-quality data training, reasonable selection of evaluation indicators (such as accuracy, recall, F1 value), regular performance evaluation and model tuning, and ensure code quality through unit testing and integration testing, while continuously monitoring the input data to prevent data drift. 3. Many measures are required to protect user privacy: encrypt and store sensitive data (such as AES

Use Seaborn's jointplot to quickly visualize the relationship and distribution between two variables; 2. The basic scatter plot is implemented by sns.jointplot(data=tips,x="total_bill",y="tip",kind="scatter"), the center is a scatter plot, and the histogram is displayed on the upper and lower and right sides; 3. Add regression lines and density information to a kind="reg", and combine marginal_kws to set the edge plot style; 4. When the data volume is large, it is recommended to use "hex"

The core idea of PHP combining AI for video content analysis is to let PHP serve as the backend "glue", first upload video to cloud storage, and then call AI services (such as Google CloudVideoAI, etc.) for asynchronous analysis; 2. PHP parses the JSON results, extract people, objects, scenes, voice and other information to generate intelligent tags and store them in the database; 3. The advantage is to use PHP's mature web ecosystem to quickly integrate AI capabilities, which is suitable for projects with existing PHP systems to efficiently implement; 4. Common challenges include large file processing (directly transmitted to cloud storage with pre-signed URLs), asynchronous tasks (introducing message queues), cost control (on-demand analysis, budget monitoring) and result optimization (label standardization); 5. Smart tags significantly improve visual

To integrate AI sentiment computing technology into PHP applications, the core is to use cloud services AIAPI (such as Google, AWS, and Azure) for sentiment analysis, send text through HTTP requests and parse returned JSON results, and store emotional data into the database, thereby realizing automated processing and data insights of user feedback. The specific steps include: 1. Select a suitable AI sentiment analysis API, considering accuracy, cost, language support and integration complexity; 2. Use Guzzle or curl to send requests, store sentiment scores, labels, and intensity information; 3. Build a visual dashboard to support priority sorting, trend analysis, product iteration direction and user segmentation; 4. Respond to technical challenges, such as API call restrictions and numbers

The core of PHP's development of AI text summary is to call external AI service APIs (such as OpenAI, HuggingFace) as a coordinator to realize text preprocessing, API requests, response analysis and result display; 2. The limitation is that the computing performance is weak and the AI ecosystem is weak. The response strategy is to leverage APIs, service decoupling and asynchronous processing; 3. Model selection needs to weigh summary quality, cost, delay, concurrency, data privacy, and abstract models such as GPT or BART/T5 are recommended; 4. Performance optimization includes cache, asynchronous queues, batch processing and nearby area selection. Error processing needs to cover current limit retry, network timeout, key security, input verification and logging to ensure the stable and efficient operation of the system.

String lists can be merged with join() method, such as ''.join(words) to get "HelloworldfromPython"; 2. Number lists must be converted to strings with map(str, numbers) or [str(x)forxinnumbers] before joining; 3. Any type list can be directly converted to strings with brackets and quotes, suitable for debugging; 4. Custom formats can be implemented by generator expressions combined with join(), such as '|'.join(f"[{item}]"foriteminitems) output"[a]|[
