Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 4239950
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 21, 20262026-05-21T03:06:07+00:00 2026-05-21T03:06:07+00:00

I’m mostly an ASP.NET developer, so I’m not very familiar with either J2EE or

  • 0

I’m mostly an ASP.NET developer, so I’m not very familiar with either J2EE or WFP best practices, patterns etc, but I feel that the project I’m involved in could have been done better, but I can’t quite put my finger exactly on what’s wrong with the architecture.

What is the best(*) architecture for a heterogenous distributed 3-tier application, specifically, if I wanted to implemented a system consisting of:

  1. Java EE 5 back-end on JBoss application server – exposes EJB services e.g. as SOAP, REST or JMS beans
  2. Hibernate to SQL Server or Oracle databases
  3. .NET 4.0 WPF desktop client
  4. .NET 4.0 Silverlight web client
  5. JSP / pure-HTML web client

* I know it’s probably impossible to define the “best architecture”, but I’m just curious about the opinions on architectural approaches, best practices, patterns etc.

One of the obvious problems I see in our design/architecture is that the SOAP Web Service communication between the .NET clients and the Java back-end is very slow, probably due to latency issues. The whole UI experience is very sluggish. And that’s with a single user – in production we expect +/- 100 concurrent users.

I’d appreciate any comments/opinions.

Some questions:

  • What technologies would you recommend to address any of the components mentioned above, e.g. what type of services (SOAP, REST, messaging?)
  • How to reduce the latency in communication between the .NET clients and the Java back-end?
  • What patterns/approaches to look at, e.g. in terms of the WPF client code (MVVM pattern?), communication with java back-end (WCF?)
  • How do you secure (authentication, authorization) such J2EE services when using a WCF client?
  • What are the architectural issues to look out for and how to address them, e.g. in terms of security, scalability, performance, etc?

(I apologize if this question is inappropriate for this site, I see a warning “The question you’re asking appears subjective and is likely to be closed”, however what I’m looking for are subjective opinions and I’m sure others who are working in a mixed .NET/Java environment would be interested.)

Thanks!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-21T03:06:07+00:00Added an answer on May 21, 2026 at 3:06 am

    The architecture for this project was too complicated.

    I would have made the following changes:

    • use .Net on the backend to reduce the number of technologies
    • drop the WPF client and use Silverlight out of browser as windows client
    • use only async calls to the backend to keep the UI responsive
    • use wcf web sockets to talk to the backend
    • use html5 as your web UI, this also supports web sockets so you have a single way to talk to your backend

    web sockets: http://tomasz.janczuk.org/

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.