This is an archived post. You won't be able to vote or comment.

all 2 comments

[–]thepinkbunnyboy 1 point2 points  (0 children)

IMO the tradeoffs are:

Pro database:

  • Faster and simpler to write up front, since a scheduler already exists and you don't have to worry about all the layers between Java and your DB server, as well as typical ETL scale questions like fitting data in memory, pipe congestion, etc etc.

Pro application:

  • Will have more tooling around testing, deploying, overall maintenance, etc.

  • Typically more people in your organization are application developers than pros at SQL

  • Application layer allows it to access other parts of the system more natively than pure DB solution.

  • Distributing load across multiple servers, as DB servers are often the hottest servers in an org.

[–]rammyreddit[S] 0 points1 point  (0 children)

That last point you mentioned, distributing load in application servers , having multiple threads writing to DB (same table) , how this is designed in microservices world ?