• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Web services architecture

 
Greenhorn
Posts: 1
Hibernate Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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!!
 
That feels good. Thanks. Here's a tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic