The organization I work with actively invests in .NET technologies, including several high-traffic ASP.NET sites that are used by internal and external clients.
We are hiring a solution architect to support these applications and work on new initiatives. Several of the renewable sources are candidates whose full experience is Java EE.
My question is, is it worth hiring the Java EE architecture when the environment we work in is mostly .NET? Are skills transferable?
Yes.
The real question is: how much?
, :
, .... (, )
Java # ( , #)
, Java .Net, , .Net. Java.
, , (.Net, Spring MVC, Django, Rails, JSF, Struts ..). Rails JSF, , , , ASP.Net , .
, .
.
10 , " ". , Java EE Architect .NET Architect, Architectating. , , . - Java EE .NET, . , - . , , , -, , -, , , , . - - . , , + . , .
, , , . , .NET Java EE, Database, , . , , . Java EE .NET, .
, - + Java EE - .NET .
, . , . , .
, Java EE .Net, ?
. , , , "!".
, , , . . , . .
-, .NET Architect, Java, . , , , .
One of my friends was a Java EE developer for a long time and switched to a .NET programmer. After 3 years, he is now a .NET Enterprise Architect and works well. However, with the number of frameworks / libraries that are in .NET (WCF, WF, WPF, etc.), there is definitely a learning curve. I think your best bet is to hire a senior programmer who has worked with .NET for several years; they will be able to introduce you to your architecture from the very beginning.