3 Broken link replaced
source | link

Using Martin Fowler's Patterns of Enterprise Application Architecture, terminology, this would be called a Gateway because it's the gate to the back-end system, and it encapsulates all the back-end interaction details. You could then see it as part of a data source layer, that decouples the M of MVC from the dirty details. If the back-end is a database, there are more specific pattern names depending on how exactly you access the database to work with the objects.

If you're fan of hexagonal architecturehexagonal architecture, you'd call this AccountManager an adapter. In the clean architecture it would be a gateway in the adapter layer.


Unrelated remark: when looking at all the responsibilities of that class, I just wonder if it's compliant with SRP.

Using Martin Fowler's Patterns of Enterprise Application Architecture, terminology, this would be called a Gateway because it's the gate to the back-end system, and it encapsulates all the back-end interaction details. You could then see it as part of a data source layer, that decouples the M of MVC from the dirty details. If the back-end is a database, there are more specific pattern names depending on how exactly you access the database to work with the objects.

If you're fan of hexagonal architecture, you'd call this AccountManager an adapter. In the clean architecture it would be a gateway in the adapter layer.


Unrelated remark: when looking at all the responsibilities of that class, I just wonder if it's compliant with SRP.

Using Martin Fowler's Patterns of Enterprise Application Architecture, terminology, this would be called a Gateway because it's the gate to the back-end system, and it encapsulates all the back-end interaction details. You could then see it as part of a data source layer, that decouples the M of MVC from the dirty details. If the back-end is a database, there are more specific pattern names depending on how exactly you access the database to work with the objects.

If you're fan of hexagonal architecture, you'd call this AccountManager an adapter. In the clean architecture it would be a gateway in the adapter layer.


Unrelated remark: when looking at all the responsibilities of that class, I just wonder if it's compliant with SRP.

2 added 434 characters in body
source | link

This couldUsing Martin Fowler's Patterns of Enterprise Application Architecture, terminology, this would be called a GatewayGateway because it offers ait's the gate to a backendthe back-end system, encapsulatingand it encapsulates all the back-end interaction details. You could then see thisit as part of a data source layer, that decouples the M fromof MVC from the dirty details.

If If the backendback-end is a database, there are more specific pattern names depending on how exactly you access the database to work with the objects.

If you're fan of hexagonal architecture terminology, you'd call this "manager"AccountManager an adapter. In the clean architecture it would be a gateway in the adapter layer.

 

Unrelated remark: when looking at all the responsibilities of that class, I just wonder if it's compliant with SRP.

This could be called a Gateway because it offers a gate to a backend system, encapsulating all the interaction details. You could see this as part of a data source layer, that decouples the M from MVC from the dirty details.

If the backend is a database, there are more specific pattern names depending on how exactly you access the objects.

If you're fan of hexagonal architecture terminology, you'd call this "manager" an adapter.

Unrelated remark: when looking at all the responsibilities of that class, I just wonder if it's compliant with SRP.

Using Martin Fowler's Patterns of Enterprise Application Architecture, terminology, this would be called a Gateway because it's the gate to the back-end system, and it encapsulates all the back-end interaction details. You could then see it as part of a data source layer, that decouples the M of MVC from the dirty details. If the back-end is a database, there are more specific pattern names depending on how exactly you access the database to work with the objects.

If you're fan of hexagonal architecture, you'd call this AccountManager an adapter. In the clean architecture it would be a gateway in the adapter layer.

 

Unrelated remark: when looking at all the responsibilities of that class, I just wonder if it's compliant with SRP.

1
source | link

This could be called a Gateway because it offers a gate to a backend system, encapsulating all the interaction details. You could see this as part of a data source layer, that decouples the M from MVC from the dirty details.

If the backend is a database, there are more specific pattern names depending on how exactly you access the objects.

If you're fan of hexagonal architecture terminology, you'd call this "manager" an adapter.

Unrelated remark: when looking at all the responsibilities of that class, I just wonder if it's compliant with SRP.