Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
As Big Data term used widely to manage huge data, I want to give a try to build a small application with Big Data to understand structure and how I can start with ASP.NET technology?
Is it possible?
"Big data" is a marketing term for "highly scalable large load computing". So can you use ASP.NET for highly scalable large load computing...
Yes, and here is how (Scaling Strategies for ASP.NET Applications).
Adding to Scott's answer, apart from ASP.NET being capable of scaling to high loads with effective strategies, .NET ecosystem also provides HDInsight in Azure, which implements MapReduce programming model to query over large clusters of Data.
Azure HDInsight could closely be related to the marketing buzzword of 'Hadoop','Big Data' etc.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am supposed to develop an enterprise-class ASP.NET Web Application that supports multiple companies.
What are the pros and cons to create separate databases for each company? Won’t it very resource consuming for a server to support connections to multiple databases or it’s better to have only one database? Let’s say I have 2000 companies and each of them has 100 employees.
What is the best approach to design the system in this case?
You might be interested in the below links:
Multi-Tenant Data Architecture
Stack Exchange
SO
Pros: Much faster querying; better overall performance, security and scale-ability; easier fine tuning of each individual database, easier deployment and troubleshooting.
Cons: maintaining 2000 backup jobs
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I want to test my asp.net web api REST service that hosted in a HP-580dl and I want to measure the performance and response time when 10,000 simultaneous requests hit the service.
is there any way to do that in C# ?
Siege is a good tool for measuring load under concurrent requests: http://www.joedog.org/siege-home/
It's not written in C#, but there's no reason why it should be.
The Visual Studio load testing tools provide this functionality, and can control multiple agents in cases where you want a distributed profile and/or a greater concurrency level than a single client machine can support.
Create and run a load test
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I'd like to start working on a web-based ASP.net application to assist me with some DBA-type tasks.
I am looking for resources, books, tutorials that might show me how to get started in writing a GUI front end for a web-based application using ASP.Net and C#?
I'll need to use whichever option (MVC or Web Forms) that supports:
dynamic charts, graphs, dash boards and metrics to present data graphically
dynamic menus and options driven by database to prevent rebuilding every time a new option is added
What are ASP.NET & C# best practices for web-based application?
I think the best place to start is the ASP.NET website.
I found the NerdDinner tutorial pretty helpful to learn ASP.NET MVC, if you're looking for a walkthrough.
http://nerddinnerbook.s3.amazonaws.com/Intro.htm
Plural Sight has been an excellent resource for me.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I build a framework that is for high traffic site, the site only for other application site log records.
I used redis or file in the middle layer to cache log
In a certain period of time, the program will take cache into the database.
Because there is a large amount of data, I need a ORM what is lightweight and agile .
I use Mysql5.x, because the SQL server of the relatively high price.
I am more familiar with ibatis (for Java),but ibatis.net was not update for two years, so, ibatis.net whether can meet the requirements?
if ibatis can do it,I can reduce a lot of learning time.
Or are you any better suggestions?
c#'s new technology, I am not very familiar with, please pointing
For anything high performance, I use Dapper. It's a micro-ORM with very high performance developed and used by the very website your are seeing! (stackoverflow.com).
It has a NuGet package too, which you can install by Install-Package Dapper command in package manager console.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
I am trying to learn RavenDB and using it's .Net client. If I am not wrong I think the main reason to use NoSql database like RavenDB is speed. It seems to be very fast as it is not relational. However when I am trying to play with .Net client of RavenDB I find that all calls are REST based calls. Doesn't that slow down speed? For each call of adding document it makes some call to HILO which basically lets the .Net client know which should be the next unique number to use and then it makes 2nd call to store the actual document.
You seems to be running RavenDB in a console app, and checking what happens in a very short lived fashion.
Run RavenDB in a real app over time, and you'll see that it is highly optimized for network usage.
You only see this hilo call once per X number of updates, and that X number changes based on your actual usage scenarios.
The more you use RavenDB, the faster it becomes.