scalability

问题 I am designing an application, one aspect of which is that it is supposed to be able to receive massive amounts of data into SQL database. I designed the database stricture as a single table with bigint identity, something like this one: CREATE TABLE MainTable ( _id bigint IDENTITY(1,1) NOT NULL PRIMARY KEY CLUSTERED, field1, field2, ... ) I will omit how am I intending to perform queries, since it is irrelevant to the question I have. I have written a prototype, which inserts data into this

问题 I have one REST API through which i am allowing to user applications(azure app) to send perfmon data to my DB. Now to load test this REST API I had built one simulator application of 500 webrole with 10 instances of each(total 5000 instances) and every 1 min 50000 (approx) requests are going to post data to REST API and so i require to scale my REST API with best practices to handle this much load. Following are my test cases to scale REST API Medium - 6 Instances => can handle 300 instances

问题 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 . After finishing school in Computer Science and entering the "real world" as a software engineer working on web applications, I've become overwhelmed by the amount of information to be learned about scaling web applications properly. Some topics/questions that have recently popped up for me: RDBMS's vs.

问题 We're pretty happy with SVN right now, but Joel's tutorial intrigued me. So I was wondering - would it be feasible in our situation too? The thing is - our SVN repository is HUGE. The software itself has a 15 years old legacy and has survived several different source control systems already. There are over 68,000 revisions (changesets), the source itself takes up over 100MB and I cant even begin to guess how many GB the whole repository consumes. The problem then is simple - a clone of the

问题 We're pretty happy with SVN right now, but Joel's tutorial intrigued me. So I was wondering - would it be feasible in our situation too? The thing is - our SVN repository is HUGE. The software itself has a 15 years old legacy and has survived several different source control systems already. There are over 68,000 revisions (changesets), the source itself takes up over 100MB and I cant even begin to guess how many GB the whole repository consumes. The problem then is simple - a clone of the

问题 I have heard the 'shard' technique mentioned several times with regard to solving scaling problems for large websites. What is this 'shard' technique and why is it so good? 回答1: Karl Seguin has a good blog post about sharding. From the post: Sharding is the separation of your data across multiple servers. How you separate your data is up to you, but generally it’s done on some fundamental identifier. 回答2: In brief, imagine seperating your users_tbl across several servers. So Users 1-5000 and

问题 How can we use mqtt protocol with kafka as a message broker? The clients(android/ios/desktop java apps etc) will be producing and consuming messages using mqtt phao client side libraries which are available in different languages using kafka as a message broker. Any advice? 回答1: You can use a Kafka source connector which will stream data from an MQTT broker like Mosquitto into a Kafka cluster. See https://github.com/evokly/kafka-connect-mqtt The simplest way to run the connector is in

问题 I am trying to use Microsoft Sync Framework 2.1 on a SQL Server database. There will be a high number of concurrent end users, synchronizing with a central database server. Further specifications are: 1500 concurrent clients connect to 1 central database server Client are using MS SQL Server Express 2008 R2 Server is using MS SQL Server Enterprise 2008 R2 Short sync intervals (around 5 minutes) Database size will be 5 GB A webservice will be used as server-side SyncProvider Does anyone have

问题 I am trying to use Microsoft Sync Framework 2.1 on a SQL Server database. There will be a high number of concurrent end users, synchronizing with a central database server. Further specifications are: 1500 concurrent clients connect to 1 central database server Client are using MS SQL Server Express 2008 R2 Server is using MS SQL Server Enterprise 2008 R2 Short sync intervals (around 5 minutes) Database size will be 5 GB A webservice will be used as server-side SyncProvider Does anyone have

问题 We have an architecture where we provide each customer Business Intelligence-like services for their website (internet merchant). Now, I need to analyze those data internally (for algorithmic improvement, performance tracking, etc...) and those are potentially quite heavy: we have up to millions of rows / customer / day, and I may want to know how many queries we had in the last month, weekly compared, etc... that is the order of billions entries if not more. The way it is currently done is