Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I'm trying to get an idea as to how what I currently do (implementing enterprise services in Java) would be done in a .NET environment. In .NET, would it typically be done using:

  • IIS as the server?
  • C# as the language and WCF as the framework?
  • BizTalk as the enterprise service bus, with MSMQ as the gateways?

Has anyone implemented services in both Java and .NET, and if so, are there any major paradigm differences or is it pretty similar?

share

migration rejected from stackoverflow.com Jun 30 at 0:51

This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as too broad by gnat, user61852, MichaelT, GlenH7, Dan Pichelman Jun 30 at 0:51

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

9  
Human parser error: Buzzword limit exhausted. ;) –  Anton Gogolev Jul 19 '11 at 13:52
6  
I haven't spent much time in the Java world, but from what I have seen, the view of a .Net programmer is that Java way over-complicates the whole process. Just write your code for WCF, decorate the public methods with a few attributes, and deploy to IIS. Not much else is needed. The whole idea of an "enterprise service bus" turns our stomach. –  Joel Coehoorn Jul 19 '11 at 13:59
    
LOL, there's 4 or 5 buzzwords there, I've seen way more than that (for both Java and .NET). So if most .NET shops aren't using an ESB or message queueing server, do you have anything that provides message persistence, or do you just go with HTTP? –  Kaleb Brasee Jul 19 '11 at 15:00
2  
I've been thinking of petitioning Microsoft to rename "WCF" to "WTF", which I think is more representative of the ordeal when using it. Who's with me? –  MetalMikester Jul 20 '11 at 12:15
    
Nice, so it sounds on par with IBM MQ and Message Broker, haha –  Kaleb Brasee Jul 21 '11 at 1:12
show 1 more comment

1 Answer

I would say that IIS / WCF is the normal approach. MSMQ gets thrown into the mix when you want persistent messages. But depending on the size of the enterprise you can also get ESBs and stuff thrown in. Most ESBs, even if they come from vendors that are focused on Java (such as IBM) will support .NET endpoints.

share
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.