All geek questions in one place

Implementing functionality / code directly in the database system

Today, RDBMS packages offer a wealth of features beyond standard data storage and retrieval. SQL Server, for example, can send emails, expose web service methods, and execute CLR code among other features. However, I have always tried to limit the amount of processing my database server can only to as much data storage and retrieval as possible for the following reasons:

  • Database server is harder to scale than web servers
  • In many of the projects that I worked on, the database server is much more busy than web servers, and therefore has less backup capacity.
  • It potentially provides your database server with a security attack (such as web services).

My question is: how do you decide how much functionality or code should be implemented directly on the database server compared to other servers in your architecture? What recommendations do you have for people starting new projects?

+3
source share
2 answers

I know that Microsoft SQL Server and Oracle really use stored procedures for everything that helps encapsulate the relational architecture and creates a more procedural interface for software developers who usually don't write SQL queries that easily.

PL/SQL ( T-SQL - ), , Java PHP # .. , . . , , , .

, , , . , , , 10-15 .

, . , SQL, , . .

. , , , Entity-Attribute-Value Polymorphic Associations, . . ( ). .

+4

. , , .

. .

: " - . ". , malarkey.

. SQL, . - , .

. .

0

Source: https://habr.com/ru/post/1698065/

More articles:


All Articles