SQL is 43 years old – Here’s why we still use it today

Re:SQL is 43 years old – Here’s why we still use it today by scarface74 on Tuesday May 02, 2017 @08:42AM (#14245858)

I've reached a point where my default design is relational database augmented with memcache/redis. The relational DB is the authoritative source of truth, redis absorbs all (most) reads and memcache is, well a distributed cache. Writes go to both redis and relational. Redis data can always be rebuilt, and is regularly rebuilt, from relational data.

I'm really becoming a big fan of CQRS/event sourcing where we have two read models - one NoSql for live data and one relational for BI/Reporting. Events are stored separately in JSON because that's how they come in anyway through the API.

[ Parent | on HN ]

Re:SQL is 43 years old – Here’s why we still use it today by remotehack on Tuesday May 02, 2017 @10:27PM (#14252558)

Wow. Let the maintenance begin.

[ Parent | on HN ]

Re:SQL is 43 years old – Here’s why we still use it today by scarface74 on Wednesday May 03, 2017 @09:25AM (#14255424)

CQRS is not rocket science. In any case, your schema for your reporting database is usually different from your online database.

[ Parent | on HN ]