Web service is not a universal method for multi-platform interaction (this sentence seems to have a language problem)

80%. net, Java/J2EE heterogeneous platform interaction will select Web service, but it cannot meet the integration requirements of a deeper level of heterogeneous platform.
Among them, execution efficiency and convenience are the key. At this time, Web Service is not the best choice.

In applications with loose connection and integration, communication between heterogeneous systems or platforms through intercommunication is better than directly calling APIs. WebService is applicable to this scenario.
However, WebService is obviously no longer used in applications with compact, heterogeneous integration or in-process integration.

Some middleware (bridging middleware) can be considered in such systems ). For example, integration servers or enterprise system buses [ESBs] can execute the. NET feature J2EE extension platform and multi-language integration technology.

John Rymer lists some deep integration scenarios.
For example.. NET application host and components running on the Java/J2EE server, and run on the Java/J2EE server. NET features, integration. net and Java/J2EE objects and components, using a setCodeIt can run on both. NET and Java/J2EE platforms.
For example, if you have created an application using. net, you must run the application on a Linux server.
In these scenarios, if we still want to use WebService, it is clear that it cannot satisfy us.