Web-service Architecture and Functionality

Question

Web-service Architecture and Functionality

Navigation

#1 by (0 votes)

0

I have a question regarding Web-service.

This is the following I have an application in Java EE JSP, where it should allow a conversation with another application on Android (Example: when registering a meeting ata in the database by the JSP application, notify in Android APP and have a user option see the status of the meeting report).

I do not know, if it is correct: I created a Web service within the JSP project, which is ready (this project makes several transactions like registering, querying, changing and deleting data, etc.).

The question is should I have three applications for communication between it?

1st to create an independent Web-service, to integrate the JSP project with the Android project;

2nd Independent JSP Project and Independent Android Project.

java web-service jsf jsp

asked by anonymous 12.05.2017 / 09:13

1 answer

Discussion on software architecture ajax without query permission

score 0 · Answer 1

Joshua,

Yes, your thinking is not incorrect, in fact, it's even a common architecture. I will advise you on the focus of each project so that the responsibility of each project is well defined and so that you can better absorb the opportunities.

Think about centralizing all the business model and rules in the web service model layer. In several situations this will make it easier to maintain when any rules change, since you only need to update 1 project.

The Android application and the JSP project will be simple, focusing more on the visual. Which is good especially for the Android application, because depending on the type of processing you need to do, a server is obviously more robust than a smartphone or tablet (but I believe not the case for your project, just an additional thought) .

You could even do the web service and the JSP project in a single project, because following the MVC, what would be your JSP project would be more focused on the View and the Controller could be implemented in the format RestFUL, for example, and so would allow an Android application to make requests to it. It is a case to evaluate the possibility.

From what I could understand of your problem, I believe these are information that would make you reflect a bit more. Anything leave a comment!