


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

InPython,iteratorsareobjectsthatallowloopingthroughcollectionsbyimplementing__iter__()and__next__().1)Iteratorsworkviatheiteratorprotocol,using__iter__()toreturntheiteratorand__next__()toretrievethenextitemuntilStopIterationisraised.2)Aniterable(like

A common method to traverse two lists simultaneously in Python is to use the zip() function, which will pair multiple lists in order and be the shortest; if the list length is inconsistent, you can use itertools.zip_longest() to be the longest and fill in the missing values; combined with enumerate(), you can get the index at the same time. 1.zip() is concise and practical, suitable for paired data iteration; 2.zip_longest() can fill in the default value when dealing with inconsistent lengths; 3.enumerate(zip()) can obtain indexes during traversal, meeting the needs of a variety of complex scenarios.

ForwardreferencesinPythonallowreferencingclassesthatarenotyetdefinedbyusingquotedtypenames.TheysolvetheissueofmutualclassreferenceslikeUserandProfilewhereoneclassisnotyetdefinedwhenreferenced.Byenclosingtheclassnameinquotes(e.g.,'Profile'),Pythondela

To call Python code in C, you must first initialize the interpreter, and then you can achieve interaction by executing strings, files, or calling specific functions. 1. Initialize the interpreter with Py_Initialize() and close it with Py_Finalize(); 2. Execute string code or PyRun_SimpleFile with PyRun_SimpleFile; 3. Import modules through PyImport_ImportModule, get the function through PyObject_GetAttrString, construct parameters of Py_BuildValue, call the function and process return

The descriptor protocol is a mechanism used in Python to control attribute access behavior. Its core answer lies in implementing one or more of the __get__(), __set__() and __delete__() methods. 1.__get__(self,instance,owner) is used to obtain attribute value; 2.__set__(self,instance,value) is used to set attribute value; 3.__delete__(self,instance) is used to delete attribute value. The actual uses of descriptors include data verification, delayed calculation of properties, property access logging, and implementation of functions such as property and classmethod. Descriptor and pr

Processing XML data is common and flexible in Python. The main methods are as follows: 1. Use xml.etree.ElementTree to quickly parse simple XML, suitable for data with clear structure and low hierarchy; 2. When encountering a namespace, you need to manually add prefixes, such as using a namespace dictionary for matching; 3. For complex XML, it is recommended to use a third-party library lxml with stronger functions, which supports advanced features such as XPath2.0, and can be installed and imported through pip. Selecting the right tool is the key. Built-in modules are available for small projects, and lxml is used for complex scenarios to improve efficiency.

When multiple conditional judgments are encountered, the if-elif-else chain can be simplified through dictionary mapping, match-case syntax, policy mode, early return, etc. 1. Use dictionaries to map conditions to corresponding operations to improve scalability; 2. Python 3.10 can use match-case structure to enhance readability; 3. Complex logic can be abstracted into policy patterns or function mappings, separating the main logic and branch processing; 4. Reducing nesting levels by returning in advance, making the code more concise and clear. These methods effectively improve code maintenance and flexibility.

Python multithreading is suitable for I/O-intensive tasks. 1. It is suitable for scenarios such as network requests, file reading and writing, user input waiting, etc., such as multi-threaded crawlers can save request waiting time; 2. It is not suitable for computing-intensive tasks such as image processing and mathematical operations, and cannot operate in parallel due to global interpreter lock (GIL). Implementation method: You can create and start threads through the threading module, and use join() to ensure that the main thread waits for the child thread to complete, and use Lock to avoid data conflicts, but it is not recommended to enable too many threads to avoid affecting performance. In addition, the ThreadPoolExecutor of the concurrent.futures module provides a simpler usage, supports automatic management of thread pools and asynchronous acquisition
