I don’t know if it’s possible to make general comments about such a solution, since it really depends on what you are trying to do and how high priority NFR lists such as performance and response time apply to your application.
If you have many users downloading a large number of binary files with a system serving a large number of downloaded binary files, then you have a situation where the cost of storing files in a database includes:
- Large Binary Files
- Costly Inquiries
Benefits
- Atomic fixation
- ( w MySQL ..)
- ..
, ,
Grails, . , , , , (, , , ).
→ . (, , GSP ). Apache , . , , , , .
, , , , , .
, , . , , . , , yyyy/MM/dd/image.name.jpg, .
, , , , , BLOB, .