• Post Reply Bookmark Topic Watch Topic
  • New Topic

Java Technology Stack for SOA App

 
Sumukh Sharma
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

I have to build a SOA based application. It is going to have a UI but majority of the operations will be for web services. This application will act as a gateway to talk to other internal/external data sources/tools/applications through web services. So the bottom line is that - heavy lifting on web services is required. I thought this will be the best forum to get an expert advice on what Java Technology (API's, Frameworks, Paradigm) should I use based on my requirements. Below are few bullets which just popped out of my head:

1. High number of transactions (so fast processing is a needed)
2. Large volume REST/SOAP messages for example, Attachment Handling
3. Mapping of REST/SOAP messages to POJO's (not sure if that's a good practice but will definitely make my life a lot easier)
4. Supporting different types of Authentication Schemes
5. Hosting web services for internal/external applications

Any and every help is highly appreciated.

Thanks.
 
Anindya Roy
Ranch Hand
Posts: 76
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you want faster response, multiple data types supported, non-transactional, only with http/https protocol to transfer, client side cache then you can think of REST


If you want distributed, transactional or two phase commit support, only xml format support, multiple protocol supprted, reliable transfer then you can think of SOAP service
 
Ulf Dittmer
Rancher
Posts: 42970
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to the Ranch.

It's hard to make recommendations because the requirements (such as they are, they need to become much more detailed before you can even design such an app, much less start to select technologies and APIs) are quite high-level and generic. Some of the items you need to determine are ballpark numbers for #1 and #2, the details for #4 (which auth. schemes? encryption as well? other security requirements?), and for #5 (are there multiple geographically distributed servers involved? what flexibility is required in hosting? what other applications do you need to interface with?) etc. Also, what are the requirements for the "UI" you mentioned?
 
Sumukh Sharma
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
@Anindya Roy - Thanks for your response but I my question is not about REST Vs SOAP. I was asking about the best API's and frameworks which I should use in building this application. I'll have to support both REST and SOAP in this application.

@Ulf Dittmer - Thanks a lot for your response. And I agree with you that requirements are too generic for recommendations so sorry about that. Please find my inputs below:

1. High number of transactions (so fast processing is a needed) - Depending on the subscribers this can vary between 60,000 to 600,000 per day.
2. Large volume REST/SOAP messages for example, Attachment Handling - Handling attachment of 15 MB to 30 MB via SOAP
3. Mapping of REST/SOAP messages to POJO's (not sure if that's a good practice but will definitely make my life a lot easier)
4. Supporting different types of Authentication Schemes - Basic, SSL, Digest Authentication (OAuth 1.0a), including request signatures
5. Hosting web services for internal/external applications - There are no geographically distributed servers for now but I would like to have that flexibility for future. The other application are the ones which will be subscribing to my web services and also the ones from which I will be pulling in the data. So its going to be both inbound and outbound.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!