architectural programming durek concept diagram

ARCHITECTURAL PROGRAMMING DUREK CONCEPT DIAGRAM CODE

ARCHITECTURAL PROGRAMMING DUREK CONCEPT DIAGRAM CODE

But is it really relevant? Shouldn’t we have most of the Front End logic as pure Javascript or Typescript code completely independent from the UI framework or library which we will eventually end up using? I had the feeling this was possible, but wanted to try it for real. In addition to bringing some fun, building a card game app is an opportunity to see these architectural concepts in action with real code and increase the level of confidence on the possibility of applying such concepts to real business scenarios.But, even in such cases, it is possible for developers to run BDD test suites on their laptop, without complex setups and, at the same time, granting a high level of confidence. In these scenarios more than one client is connected to the app and uses it concurrently with other clients, which makes testing more challenging. The third concept is about testing, in particular testing interactive multi user scenarios.We want to use a reactive model and check up to which point we can move our logic to a pure Javascript / Typescript layer minimizing the dependencies on the specific library / framework we choose to use. The second concept is on the Front End.The best deployment model to adopt depends on the context, so it is important to stay flexible and minimize the effort needed to move from one deployment model to another if circumstances require a change. The first concept to test is flexibility when it comes to deploying in the cloud.A real time card game involving more than one player represents a good playground to exercise some architectural concepts: flexibility in cloud deployment models, reactivity in the front end, testability of complex scenarios.

Architectural programming durek concept diagram