Learn how to design large-scale systems

Re:Learn how to design large-scale systems by tomnipotent on Friday July 13, 2018 @01:27PM (#17524898)

Like all things, it depends. Certain features/abstractions have more value at different stages of an application.

I LOVE using views early on in a new application's schema as it allows me to evolve the logical model separately from the physical model, and once I've coalesced on something I like it's easy enough to swap the view with a real table and my application code higher in the stack is none the wiser.

Even Facebook at one point relied on MySQL triggers to keep its memcache fleet synced.

[ Parent | on HN ]

Re:Learn how to design large-scale systems by scarface74 on Friday July 13, 2018 @01:49PM (#17525073)

Views aren’t quite as bad as stored procedures. I could see doing a view being decently easy to manage - you can always add s column without breaking backwards compatibility. But you can’t imaging the number of times I’ve seen things like...

SaveCustomer_1 SaveCustomer_2 SaveCustomer_3

And you never know whose using what.

[ Parent | on HN ]