
#include <iostream>
#include <stdexcept>
#include <string>
#include <vector>
using namespace std;
//entity
class OrderLine {
string sku;
int price;
int count;
public:
OrderLine(string sku, int price, int count)
: sku(sku), price(price), count(count) {
if (count <= 0) {
throw invalid_argument("bad count");
}
}
int cost() const {
return price * count;
}
};
//entity
class Order {
int id;
vector<OrderLine> lines;
bool isPaid = false;
public:
explicit Order(int id): id(id) {}
int number() const {
return id;
}
void add(const string& sku, int price, int count) {
lines.push_back(OrderLine(sku, price, count));
}
int total() const {
int sum = 0;
for (const OrderLine& line : lines) {
sum += line.cost();
}
return sum;
}
//business rule: 10% off from 200
int discount() const {
return total() >= 200 ? total() / 10 : 0;
}
int payable() const {
return total() - discount();
}
//business rule: an empty order is never paid
void pay() {
if (lines.empty()) {
throw logic_error("empty order");
}
isPaid = true;
}
bool paid() const {
return isPaid;
}
int size() const {
return lines.size();
}
};
//client code
//no database and no screen anywhere above, and no
//header beyond the standard library
Order order(1001);
order.add("pen", 30, 2);
order.add("lamp", 190, 1);
cout << "order " << order.number() << endl;
cout << "lines " << order.size() << endl;
cout << "total " << order.total() << endl;
cout << "discount " << order.discount() << endl;
cout << "payable " << order.payable() << endl;
order.pay();
cout << "paid " << boolalpha << order.paid() << endl;
//a line that breaks the rule never gets into the order,
//so the order below stays empty and is refused too
Order empty(1002);
try {
empty.add("pen", 30, 0);
} catch (const invalid_argument& error) {
cout << "refused: " << error.what() << endl;
}
try {
empty.pay();
} catch (const logic_error& error) {
cout << "refused: " << error.what() << endl;
}
//printed: order 1001
// lines 2
// total 250
// discount 25
// payable 225
// paid true
// refused: bad count
// refused: empty order
An entity holds a business rule of the shop and knows nothing about a database, a screen or the network, so it can be tested without them.Read moreThe problem. A shop gives 10% off every order from 200. If this rule lives in a web page, and again in a database query, the two copies soon disagree. To check the rule, you must start the page or the database. The most important knowledge of the shop is scattered and hard to test. The idea. An entity is a piece of data together with the business rules about it: what an order contains, how its total is counted, when it may be paid. It knows nothing about a database, a screen or the network. Clean architecture has one main rule, the dependency rule: outer code may know inner code, but inner code never knows outer code. Entities are the innermost code, so they depend on nothing. How to read the example. There are two entities: a line of an order and the order itself. The order sums its lines, gives 10% off from 200 and counts the amount to pay. It refuses to be paid while it is empty. The client code builds order 1001 with two lines and prints its numbers: the total is 250, the discount 25 and the amount to pay 225. It also tries to pay an empty order, and the entity refuses. In some languages the entity is a plain value with functions, not a class; its role is the same. When to use it. Make an entity for each concept of the business that has its own rules, such as an order or an account. Data without rules needs no entity: a simple structure is enough. A common mistake. An entity that saves itself to the database or formats itself for the screen. Then it depends on outer code, and its rules can no longer be tested alone. |