web-architecture | 易学教程

Horizontal scaling of JSF 2.0 application

阅读更多关于 Horizontal scaling of JSF 2.0 application

问题 Given that JavaServer Faces is inherently stateful on the server side, what methods are recommended for horizontally scaling a JSF 2.0 application? If an application runs multiple JSF servers, I can imagine the following scenarios: Sticky Sessions: send all requests matching a given session to the same server. Question: what technology is commonly used to achieve this? Problem: server failure results in lost sessions... and generally seems like fragile architecture, especially when starting

Does ST(State Transfer) in REST mean that state must be held by client?

阅读更多关于 Does ST(State Transfer) in REST mean that state must be held by client?

问题 I read What does “state transfer” in Representational State Transfer (REST) refer to? and several post or videos about REST, and I know one of the constraint of REST is stateless. According to many posts like http://www.restapitutorial.com/lessons/whatisrest.html ,to make the architecture stateless, the client must hold the enough information for the server to do the right thing, which means the server does not have any client state. So does it mean we are only about to build a REST

Can i say that MVP = 3 Tier Archi?

阅读更多关于 Can i say that MVP = 3 Tier Archi?

问题 From last few days i have been searching the optimal architecture for my new web application, which would be devloped in ASP.Net using C#. Until now, i only find and study following 3 Three Tier Architecture (Note: By Tier i mean logical layer) Model View Controller (MVC) Model View Presenter (MVP) Now folling are my questions: 1) As far as i understand 3 Tier Architecture and MVP can I say that MVP and 3 Tier are the same thing? If not, then what is the difference bewtween both? (Note: I

Load testing ZeroMQ (ZMQ_STREAM) for finding the maximum simultaneous users it can handle

阅读更多关于 Load testing ZeroMQ (ZMQ_STREAM) for finding the maximum simultaneous users it can handle

问题 Does anyone have any real-world scenarios that load-tested ZMQ sockets for maximum no. of 'concurrent users' (not throughput) they can handle? Looks like ZeroMQ has some serious problems with FD limits. The scenario is: there are numerous web-server frameworks out there that are boasting of millions of concurrent users they can handle - now if ZeroMQ cannot handle beyond FD_SETSIZE no. of users at any point of time, it is a very serious restriction on scalability (since FDs are not just

Web architecture: MVC, Lazy initialization, Data transfer Objects, Open Session In View, is there a consensus approach?

阅读更多关于 Web architecture: MVC, Lazy initialization, Data transfer Objects, Open Session In View, is there a consensus approach?

问题 What flaws do you see in the following design, (and what would be your ideal architecture suggestion) for a typical web 3-tier application? My current blueprint approach is very roughly this (assuming Java, Spring, Hibernate, JSP) Controller Stateless, potentially wrapped with a read only transaction (to avoid lazy init exceptions), get's entities from persistence storage via the service only, passes them to the view as the model. Conducts business logic on them (should the BL be in the

Does ST(State Transfer) in REST mean that state must be held by client?

阅读更多关于 Does ST(State Transfer) in REST mean that state must be held by client?

I read What does “state transfer” in Representational State Transfer (REST) refer to? and several post or videos about REST, and I know one of the constraint of REST is stateless. According to many posts like http://www.restapitutorial.com/lessons/whatisrest.html ,to make the architecture stateless, the client must hold the enough information for the server to do the right thing, which means the server does not have any client state. So does it mean we are only about to build a REST application only through putting some user state in the client like cookie? But according to many posts like