Implement business services in PL / SQL or Java? Favor / Cons?

Question

I work for an enterprise that will build a web services stack architecture (based on the wait principle), I am a technical manager. This architecture will be created using the Java platform, but I have a problem with some team members: they are from the old school of Oracle (i.e. they used the legacy using PL / SQL, and based on them, the business logic should only be in the database data, with only a small level of java that causes this), I have some arguments about this, but I would like to know your arguments in favor or cons in the question.

Java Favor (in my opinion)

• Scalability
• Monitoring
• Object oriented language
• Synchronization Process / Async
• Rich domain
• Testability

Answer 1

You can find the following interesting and useful articles:

• Working definition of business logic with implications for CRUD code
• Business logic: from working definition to strict definition
• Business Logic Theorems
• Can you create a business logic level?

Answer 2

I worked on such a project using MS SQL, not Oracle. It was not a pleasant experience. The problem is that T-SQL is not a very modern language, so we were not as productive as we could be, and there was more code duplication than otherwise.

There is an argument that developer productivity is more important than lang, so if these guys are just so good, so what. But you will not find many young developers who want to work that way.

Answer 3

It must be a court decision. Any of these may be more appropriate based on use. For a simple example

If you have a business rule that requires data from several tables and based on the data received, it decides to perform the final operation with the database (insert or update), then, in my opinion, the pl / sql procedure is the place to do it . Since this will save time and bandwidth n / w and will be faster.

Answer 4

This is a bit complicated question, but very thought-provoking.

Starting with Oracle 9i, it has full support for Java Stored Procedures, i.e. you can store Java classes inside the database server and execute them when you execute Pl / Sql procedures.

It would always be a good option to choose the perfect employee, rather than stick to the mood! Since you stated that Java has the presence and support of universal concepts in different domains.

Here I can come up with the following options for the optimal solution, acceptable to everyone.

• Write the necessary procedures in java, save them on the server
• Write at least the basic requirements that really reduce the complexity of the task compared to Pl / Sql and call them in Pl / Sql
• Without pollution, it does not support separate layers, which is the second best option.