This week's book giveaway is in the Mac OS forum.
We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line!
See this thread for details.
The moose likes Web Services and the fly likes Web services architecture Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » Web Services
Bookmark "Web services architecture" Watch "Web services architecture" New topic
Author

Web services architecture

Shrimant Damodarpant
Greenhorn

Joined: May 02, 2013
Posts: 1

Hello Experts,

I need some opinion and inputs on the architecture I am suggesting to my project as below.

I have an UI built using HTML/JavaScript which will be hitting database in following manner -

UI (JSON over HTTPS) >> [Web Tier: JSON to Java Objects > Spring MVC (front controller) > Web Service Client] >> [App Server: Web Service > Authenticate > App Service] >> [DAO > DB]
UI (JSON over HTTPS) >> [Web Tier: JSON to Java Objects > Spring MVC (front controller) > Web Service Client] >> [App Server: Web Service > Authenticate > App Service > Web Service Client] >> [ESB: Web Services with business logic] >> [DAO > DB]

Requirements:
1) The business logic needs to be on web services on ESB so that other system can reuse them
2) App service can be wrapped under Web Service to be able to use by other systems if required.


Please let me know if this architecture has any issues or can be improvised...many thanks in advance!!
 
Don't get me started about those stupid light bulbs.
 
subject: Web services architecture