Java – Service Architecture – WebServices | SOA

I would like to know which method is most suitable for managing the following schemes

For example, there are 25 applications mainly in Java and deployed on different platforms based on Web, such as JBoss and WebSphere Tomcat Each application exposes 3 - 5 services and also consumes services from other applications Most of them are synchronous and triggered on an as needed basis Here are some use cases,

>When a patient is admitted, this will send messages to 4-5 systems that are interested in admission details (synchronization). > Billing system sends details to another system to calculate discount (synchronization) > get patient details by passing identity (synchronous)

So if you try to represent the entire diagram in picutre, it's like many hard coded static lines between each system

problem

>You can't find a common method for the health of each system or web service until users complain that something doesn't work. > Too many web services and endpoints can be tracked. > Due to the difference between application servers and containers, it is implemented on diff standards Jax WS and Jax rs. > Some messages are the same, but the details are slightly different As a result, reusability is reduced and new services are eventually provided for each custom requirement

What kind of solution is more suitable for solving the above problems?

Solution

This is a difficult and common problem for large enterprises What you can see is the integration of enterprise service bus into your company to promote SOA You can then implement adapters for each system in the ecosystem Adapter interfaces will be strictly controlled, documented and standardized

About checking system health You can view and use platforms such as Nagios You need to identify harmless web services (for example, basic reads) that can be used to determine whether a given system is "up" Then Nagios can call regularly