New answers tagged

4

"Too complex" is a common concern for new developers, but consider that this is a working solution for them right now. Working now beats better in six months, nine times out of nine. Also, as a new developer, please consider that re-implementing anything from scratch will take several times longer than you expect, is statistically unlikely to fulfil even the ...


0

I think you could move all behaviour which are depend on context (where the link is rendered) into the separate 'strategies'. Link provides public API (e.g. add/remove/change icon) which strategy could use in order to change the link. In terms of Angular it might be @Decorator which in constructor takes the Link instance and call link public methods. In ...


1

There are two issues here: You don't want a overwrite changes made by one user with changes and old data from another user. You don't want users viewing and making decision base on old data. The first issue is crucial and can be addressed without dealing with 2. What I would recommend here is generally called 'optimistic locking'. You assume that you ...


2

Based on this definition of an n-tiers architecture, a tiers is a multilayered architecture where the layers are made of components. In fact, this definition proposed by one of our peers is very close to the more generally accepted definition used in scientific literature: A Multi-tier Architecture is a software architecture in which different software ...


3

The challenge in answering this question is that we are dealing with terms, in this case "tier", that have imprecise meanings and different people use the term differently. For example, a common view is that there is a distinction between layers and tiers. A layer is an abstract separation, as in the controllers, business logic and data objects in your ...


1

Do the figures specify the presentation/application/data logics? If so, how? They don't specify them in any precise sense, but they do show a high level logical organization of the system. Presentation logic would be a part of the user-facing tiers (desktop GUIs, web pages, mobile device screens). Most of the application logic would be in what's on both ...


1

MVC (model-view-controller) is an architectural pattern, but it does not map directly into N-tier architecture: Those are more or less orthogonal, and in principle each layer can have their own (even multiple) MVCs. And of course N-tier architecture can use MVC somewhere or not. For some simplified system, maybe one can somehow put model at some business ...


Top 50 recent answers are included