Building an enterprise level application

Question

0.00/5 (No votes)

See more:

, +

Dear all experts,

This might seem to be a very broad question, but, I will give it a try to explain my situation.

I want to build an enterprise level web application. Key features and scenarios would be;

1. Millions of user and user related records stored in a normalized database (prefer SQL Server)
2. Any number of authorised client machines can access these records at any given time
3. There will be no geographical limitation in order to access these records
4. File transfer (upload/download) must be possible via the web client

The above are very broad level requirements for the application as a whole.
I am a web developer - developing using C#, ASP.NET and SQL Server. I am aware that this is possible via above technologies.

But, my main concern is the time latency to access required records on the top of normal asp.net page load and weight.

I therefore thought of using web services to get the data and display in the page. I am thinking of using JSON to call the web service and retrieve/display data. Am I doing it right in terms of using JSON or should I consider anything else.

If you could shed some light on this, it would be great and if you have any further questions, feel free to ask as well.

Thanks in advance.

Cheers,
Nayan

Posted 15-Dec-13 15:47pm

Nayan Ambaliya

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ron Beyer · Accepted Answer · 2013-12-15T15:55:00

Solution 1

Once you get to a user base like that, you will have a load balancing server setup, distributed SQL servers, and other network tricks to maximize your network throughput. This is what you'll (handsomely) pay a good network admin for.

It isn't so much about the design of the web app at that point, there is only so much code can do, the rest has to be taken care of by hardware.

Posted 15-Dec-13 15:55pm

Ron Beyer

Comments

Nayan Ambaliya 15-Dec-13 21:56pm

Hi Ron,

Thanks for your input. What I was really concerned is all about JSON. Am I right by using JSON as an in page technology to trap the data everywhere.. ?

Thanks.

Ron Beyer 15-Dec-13 22:00pm

I'm not sure I can answer that, if you are talking about JSON between your SQL server and your web app, then I would say you just want to work directly with the SQL data instead of trying to add another layer of abstraction. It really depends on what the producer of JSON is and what the consumer is, if its all internal, try to minimize pieces between your presentation and your backend.

Nayan Ambaliya 15-Dec-13 22:06pm

Hi Ron,

Thanks for the prompt reply.

Ya, I got your point, but, I think, executing data requests via C# directly to SQL via business and data layers would be time consuming and heavy while, using JSON via web services would atleast load the page with data loading indicator. Over the top, JSON is light weight as well which will minimize load on the page.

All request will be outside and nothing is internal here..
What you think ?

Thanks Ron

Ron Beyer 15-Dec-13 22:10pm

Maybe a more responsive back-end is what you are looking for, instead of web services. I would look at things like Reactive Extensions and Ajax to use quick page loads while loading data in the background and notifying the page when ready.

Nayan Ambaliya 15-Dec-13 22:12pm

hmm.. I think you made me think in another direction now with more questions.. I totally take your point, but what I was thinking of using these web services somewhere else (in terms of UI) just to use the same code for multiple UIs.. I think I forgot to mention that in my initial question.. What do you think now..

Ron Beyer 15-Dec-13 22:27pm

Whatever you can do to maximize code re-use or consolidate pieces is a good thing, somebody with a little more experience in web services will have to answer that though.

Nayan Ambaliya 15-Dec-13 22:37pm

Thanks Ron, I will take it from here..
Thank you very much for your inputs.

Regards,
Nayan