Vertabelo's blog covers database design, SQL, and data modeling, and promotes its online database modeling tool.
HN commenters link its data model walkthroughs and its article on business logic in the database, and discuss its SQL pronunciation post.
I think the jury's still out on that one. I've always spelled it out (and I always will, dammit!), I've had professors either spell it out or pronounce it, and it very much seems to be a mix of regional preference and past experience. Of course, there's two arguments here: One is that SEQUEL was changed to SQL to avoid possible trademark issues (thus implicating that this also necessitated a change in the pronunciation), the other is that the original intent was to call it SEQUEL (thus this is the Only Way). Which is more correct? No one knows!
There's an interesting write-up on the differences[1] which I find interesting. There's even a fellow who asked one of the original developers[2] how to best pronounce it (spoiler: no resolution).
Come to think of it, I spell out most acronyms under 4-5 characters much to the chagrin of my peers (unless the intent was clearly to make it a word). I think it ought to boil down to preference.
[1] http://www.vertabelo.com/blog/notes-from-the-lab/sql-or-sequel
[2] http://patorjk.com/blog/2012/01/26/pronouncing-sql-s-q-l-or-sequel/
I always like to link these articles when the topic comes up:
https://sivers.org/pg
https://www.vertabelo.com/blog/business-logic-in-the-database-yes-or-no-it-depends/
https://www.martinfowler.com/articles/dblogic.html
There is also this video on how to properly architect these kinds of applications: https://youtu.be/PMPW024NIDE?t=1052
"Best" is tricky, but Vertabelo have been doing practical data model design walkthroughs for various scenarios over the past year or two: http://www.vertabelo.com/blog .. things as diverse as data models for a 3D chess set, parking system, pet care company, office leasing, etc.
Thank you for sharing your thoughts on the two.
You might find Vertabelo [1] useful and possible replacement of LucidChart & Visio for db modeling.
[1] http://www.vertabelo.com/
Another article on the same: http://www.vertabelo.com/blog/notes-from-the-lab/business-logic-in-the-database-yes-or-no-it-depends