-
Is it important for choosing correct framework that our application is absolutely stateless? We don't need to worry about synchronization, single thread model etc
-
I prefer a model where we write "regular" services layer. I mean that services are not aware about web framework and are synchronous. This approach simplifies development and testing of those services. And then "Controllers" layer calls those services in async way. Am I right when I want to achieve such architecture or it has some drawbacks?
-
I prefer that web framework will have a controller, which returns async result to the framework (like returning Futures in akka-http or Flux in Web Flux) instead of Vertx approach of handlers, because handlers take more code lines and are less readable. Am I right? Do i miss something?
If you thing that I'm right in 2. and 3. - which framework works in such way?
If you don't agree with 2. and 3. - which considerations should I take?
Aucun commentaire:
Enregistrer un commentaire