php处理用户,php – 如何处理复杂的用户状态？

有趣的问题,但也没有一个单一的答案.

我认为这里的复杂性可能来自周围的代码,而不是核心业务逻辑和需求.我这样说是因为三种状态类型都是从内部应用程序派生出来的,并不是太糟糕.

一种可能的解决方案,我假设某种程度的MVC或类似.

鉴于你的模型,用户,并扩展像Eloquent这样的ORM(我会从Laravel Eloquent,因为我最熟悉它,但任何ORM都可以工作)：

use Illuminate\Database\Eloquent\Model;

use App\DebtCollector;

public class User extends Model

{

// Assuming model has the following fields

// id, status, registration_date, and a one to many

// relationship with debts

protected $fillable = [

'raw_status',

'registration_date',

];

public function debts()

{

return $this->hasMany(Debt::class);

}

public function refreshStatus()

{

$dc = new DebtCollector();

// Business logic inside the "DebtCollector" class

$this->raw_status = $dc->resolveStatus($this->debts, $this->registration_date);

// Save value to the underlying datebase

$this->save();

}

// If you fetch a status directly, it will refresh first,

// then return the value

//

public function getStatusAttribute()

{

$this->refreshStatus();

return $this->raw_status;

}

}

// Schedule task somewhere - ran nightly, or whenever

//

// This way you can refresh the status only on certain groups

// of data - for example, if the business flow means that once

// they become compliant, they can't go back, there is no need

// to refresh their status anymore

//

User::where('raw_status', '<>', 'compliant')->refreshStatus();

// Alternatively, the schedule could chunk results and do an update

// only to those not updated in the last 24 hours

//

$date = new DateTime;

$date->modify('-24 hours');

$formatted_date = $date->format('Y-m-d H:i:s');

User::where('last_updated', '>', $formatted_data)->refreshStatus();