scalability

问题 I've been arguing with some friends on the university, and we can't get to a point to which is the framework with more scalability for web applications (and still very fast). One calls for jsp, the other one for ruby other for php and so on. Could i ask you to clarify us on what as more scalability potential? Tks, hope I'm not duplicating anything I've searched but didn't found any previous question like this. Edit: If you could point a comparison about this it would be good :) 回答1: Ruby and

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 4 years ago . In many projects we are developing we need to have CMS functionalities in the back end of the site. On the other end we don't want to or can't commit to a complete front end solution. To explain this better: CMSes like Joomla or DotNetNuke are complete web site solutions, they let you store and publish data.

问题 I tried to test RabbitMQ, but I found that rabbitmq has some problems: if I created a cluster of 3 nodes, I can't publish/delivered more than 6000/s. in other hand, if I worked with one single node, I can publish/delivery until 25000/s. which means, more that I add nodes, more performance is deteriorating. but from this article : https://blog.pivotal.io/pivotal/products/rabbitmq-hits-one-million-messages-per-second-on-google-compute-engine they can publish more than 1 million, so how they can

问题 I want to build a RabbitMQ system which is able to scale out for the sake of performance. I've gone through the official document of RabbitMQ Clustering. However, its clustering doesn't seem to support scalability. That's because only through master queue we can publish/consume, even though the master queue is reachable from any node of a cluster. Other than the node on which a master queue resides, we can't process any publish/consume. Why do we cluster then? 回答1: Why do we cluster then? To

问题 I want to host my WCF services in the Azure clouds for scalability reasons. For example there will be service for user authentication. And it will be under High Load (1000+ user/sec). Does anybody here have real experience with hosting WCF services in the Azure cloud with high user load? What are best practice, patterns here? Does Azure has some cloud balancing API for such tasks? Thanks, Kirill. 回答1: EDIT April 9, 2014 - updated with latest scalability targets The Windows Azure load balancer

问题 I want to host my WCF services in the Azure clouds for scalability reasons. For example there will be service for user authentication. And it will be under High Load (1000+ user/sec). Does anybody here have real experience with hosting WCF services in the Azure cloud with high user load? What are best practice, patterns here? Does Azure has some cloud balancing API for such tasks? Thanks, Kirill. 回答1: EDIT April 9, 2014 - updated with latest scalability targets The Windows Azure load balancer

问题 I want to host my WCF services in the Azure clouds for scalability reasons. For example there will be service for user authentication. And it will be under High Load (1000+ user/sec). Does anybody here have real experience with hosting WCF services in the Azure cloud with high user load? What are best practice, patterns here? Does Azure has some cloud balancing API for such tasks? Thanks, Kirill. 回答1: EDIT April 9, 2014 - updated with latest scalability targets The Windows Azure load balancer

问题 I store different items (notes, articles, pictures, files) in a single table (there are many metadata in common for all the item types - for example, categories, tags, rating, statistics etc.). My first design was like this: table Items , plus another "detail" table for each of the item types ( NoteItems , ArticleItems , PictureItems etc.). To retrieve a single item, tables must be joined one-to-one (SELECT * FROM Items INNER JOIN PictureItems ON Items.Id = PictureItems.Id WHERE Items.Id = N)

问题 I maintain a web application that is outgrowing a single VPS. The architecture consists of a large number of small users, each with their own subdomain. Users do not interact. Load means i have to move some users, and all new users, to another installation of the web application on a separate server. Currently, every user subdomain falls to the same virtualhost, where a single PHP front controller displays the appropriate content based on the hostname. A single wildcard DNS record for *

问题 I am having issues with a CoreData-based iOS app when it tries to build the initial DB from data sent from the server. Basically, the server sends down 1MB chunks of objects (about 3,000 per chunk), and the iOS client deserializes them and writes them into disk. What I'm seeing is that everything is going pretty well for about the first 8 chunks (out of 44), then performance drops off dramatically and each chunk starts taking longer and longer, as in the image below. Pretty much all the time