PO VO DTO BO in Java

PO persistent object, data;

BO business objects, encapsulated objects, complex objects, which may contain multiple classes;
A DTO transmits objects, which are transmitted at the front of the call;
VO performance object, front-end interface display.

When your business is simple enough, a pojo also looks exactly like Po BO DTO VO, here's an example:
For example, there is a user class with only name and phone
For the database level there are two columns, the business plane, the transmission, and the front desk show only these two items.

And then say the examples they distinguish:
1, or the user class name phone added a password.
Then your back end of the PO attribute is also the 3, the general database of the table has a few fields of how many properties of your PO, but transmission to the foreground or display, we should not put password password This thing also passed, so their dto VO is still name + phone
Po:name Phone Password
Dto:name Phone
Vo:name Phone

2, now added an enumeration status bit status indicates the user's special state, the foreground will not be directly displayed, may be based on this state to produce subsequent operations,
Po:name Phone Password status
Dto:name Phone Status
Vo:name Phone

3, then look at Bo, a user below will certainly be associated with a lot of other tables
such as user settings user information, then this BO not only has the user's own properties, but also contains user settings and user information of the two classes.

Link

https://www.zhihu.com/question/39651928/answer/87536000
Http://www.blogjava.net/vip01/archive/2013/05/25/92430.html

PO VO DTO BO in Java