Tell me more ×
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.
up vote 5 down vote favorite

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|improve this 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

migrated from stackoverflow.com Jul 20 '11 at 6:09

2 Answers

up vote 1 down vote accepted

I don´t know what exactly kind of proccesses your application must support, but IIS / SQL Server / WCF forms a good triad.

MSMQ is an alternative for transactioned queues, interesting for assync proccesses.

If you choose not to use a Biztalk, take care to use Enterprise Library or another framework which provides log, instrumentation and other resources.

share|improve this answer
up vote 0 down vote

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|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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