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 6 years ago.
Improve this question
I apologize if these are bad questions, however I stumbled upon .NET remoting not too long ago and it's confusing me a little. What I've come to understand is .NET remoting is a way to call an object that is completely separate from your current program, is this correct? (My research includes reading and maybe understanding the MSDN Technical Overview of .NET Remoting).
When I stumbled upon the .NET remoting feature (here), it was because I was looking up methods for multithreading. Is .NET remoting a form of multithreading? Is it related to multithreading at all?
Thank you in advance for your time.
First of all .NET Remoting isn't a good choice if you start a new development because it was discontinued a long time ago. It's still there to provide backwards compatibility.
Since .NET 3.0, the right choice to do what did .NET Remoting has been Windows Communication Foundation.
About your concerns, .NET Remoting was a way of simulating that objects from other AppDomains and even other processes from same or other machines could co-exist like regular, offline objects in a very transparent way.
In a short summary, I would say that .NET Remoting wasn't designed for multi-threading purposes but as an inter-process communication approach.
Now with either WCF or ASP.NET Web API you can consume and emit objects between processes in the same machine or between other machines in the same or other networks. See WCF and ASP.NET Web API self-host flavors to learn how you can host a network API in your process and let other processes consume them.
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 6 years ago.
Improve this question
We are trying to create a solution for high frequency trading application on SOA. As resident of .NET, we are using WCF services. Searching Google, I found REST payload is less than the SOAP payload. REST is faster than the SOAP. At the same time, SOAP has some other advantages like Transaction support, more binding support, so on.
Which will be faster netTCPbinding with SOAP or REST with JSON?
Which one should has more advantages for high load and low latency system?
Any pointers?
Generally speaking REST has a better performance, you may check this entry Rest vs. Soap. Has REST a better performance?
Anyway for HFT this could be not enough, as Udi said, you may pay attention to your application architecture and your infrastructure, avoid closing connections, use TCP protocol directly instead HTTP, use non-blocking io technics to improve TPS, maybe using messaging systems (kind of JMS) ...
is a broad topic
For any type of low latency scenario, you should be avoiding network calls like the plague. If you really want to play in the HFT space, you'll need to handle much deeper architectural questions than the ones raised here.
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 8 years ago.
Improve this question
I am a C# .NET developer, and the tools I use to build a web application are:
SQL Server
Entity Framework
.NET Web API
ASP.NET MVC
HTML/CSS/jQuery
I have been reading up on AngularJS, NodeJS, MongoDB, and ExpressJS, and it certainly seems like with these "Javascript-ish" technologies, you can build a full blown web application.
My question is where does this leave me with my knowledge of the .NET stack? I want to start embracing these newer technologies, and build my next website with them, however, I am confused as to whether I should completely do away with the .NET stack, or if I should complement these newer technologies with the power of the .NET stack where it might make sense. Here are some of my thoughts:
MongoDB could replace SQL Server and Entity Framework
AngularJS can pretty much replace ASP.NET MVC (since both are MVC patterns, having both would be redundant, I think)
But when it comes to building an API layer, would NodeJS completely replace ASP.NET Web API? or could I use them together? What would make the most sense (generally speaking)? Considering that NoSQL databases like MongoDB have javascript-like syntaxes, do we even need server side APIs? Couldn't the client (theoretically) directly talk to the DB?
And where does ExpressJS fit in?
I am hoping someone can help to clarify how these technologies fit in with each other. Pretty sure that a lot of .NET developers looking to explore these newer technologies have the same questions.
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'll soon be looking into writing a small business workflow application that I'd like my userbase to use across all devices - iOS Tablet, Windows PC, Windows Tablet, Mac, Android Tablet are the key targets.
I'm fairly new to the 'app' dev space and I don't know much about what frameworks and industry standards are forming around PC and mobile friendly applications, if any?
I'll be writing the core of the application in C# and I'm looking for technologies (HTML5, JS, etc) and even frameworks (I saw Xamarin might be okay?) that implement the View of the application. The tighter its tied to C# the better it'll be for me and the cleaner the transition between my chosen platforms the better.
I just created one using Jquery Mobile, and an odata C# webservice. Its just what work wanted me to but I see the framework being used alot. So pretty much get the data with the webservice then use javascript and html5 to display it.
If you want to write your application in C#, and not implement it as a web service, then I think the only option is Xamarin for the iOS / Android platforms (and .NET / Mono on Windows / OS X).
This does not mean using a single technology for the View, though, as Xamarin UI code is not portable across iOS and Android (this has pros and cons involving the age-old native feel versus shared UI debate).
If you are flexible on implementing it as a web service, then your server logic can be written in C#, with a shared HTML 5 client across all platforms.
If you are flexible on using C#, then you have more options outside the scope of this question.
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 8 years ago.
Improve this question
I am looking for the best way to implement, let's say a middle tier.
In the company I working for, we have two systems written with different programming languages. Each one must communicate with a third system via xml (rest and soap).
The first thing that came in my mind was to create a web application which would accept the calls from our internal systems but I stopped this implementation as I faced some issues regards the soap serialization (How could I do this?).
Except this I thought of WCF but I don't know if it is an appropriate solution for my case.
So, I would like to know which is the best way to implement this.
I'll appreciate any comment
Thanks
You should use WCF for the middle-tier since it provides you with everything you need.
Serialization
Interoperability with Other Web Services Platforms
Interaction with Applications built on other technologies, such as J2EE application servers, that support standard Web services. These applications can be running on Windows machines or on machines running other operating systems.
Security
SOAP All Version and REST
Bindings
Protocols
Discovery
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 8 years ago.
Improve this question
I`m learning programming languages. And I decide that I need to lear a new web framework. I have 2 candidates: Django or ASP.NET MVC 2.
Can you say me the difference between them and what is so interesting?
Try both, then decide.
Well, I'm using both and found both to be state of the art, easy to learn, fast and easy to install.
Maybe don't look at it from a technical standpoint but from the context. ASP.NET needs a Windows Server, ASP.NET and an IIS installed. You have the license for that? Django on the other hand is open source runs on cheap but fast linux machines and provides you with the Python Language and it's vast easy to install moduls.
If you don't know Python or C# maybe Django is the better way to go. Djangos Documentation is great and has a great tutorial, which is yet to be found on the ASP.NET MVC side.
Well, the conclusion is: Try both :) And if you're gonna use ASP.NET MVC, watch the Nerddinner Sessions (PDC) by Scott Hanselman and Phil Haack.
I would create a small app to try each for a day or two and then choose.
I can't speak for Django, but here are some Asp.Net MVC benefits
Tight integration with other Microsoft technologies
Uses jquery out of the box
Choice of several server-side languages
Very flexible (choice of unit test framework, view engine, model architecture etc)
and a potential negative
Might take extra work getting it running on anything other than Windows
What reasons lead you to choose those
two frameworks?
What reasons lead you to choose those
two languages?
If you don't like the answers, then keep looking. Otherwise...
Do you want to be on a
non-Microsoft web stack? Go Django.
Do you want to interface with lots of other
Microsoft web stack technologies? Go
MVC.
Do you want complied language speed? Go C#.
Do you want interpreted language portability? Go Python.