2 ms·
> What you have not realized is that architecture that is hard to change later is poor architecture. In some circumstances yes others no. In my in house datab
by collyw 12y ago
> What you have not realized is that architecture that is hard to change later is poor architecture.
In some circumstances yes others no.
In my in house database, I asked a couple of years ago about the relationships between entities in the database. I got an answer, I designed (architected?) it from there. The database tracks samples for a DNA sequencing centre. Now a couple of years later, the technology has changed. And where it was a one to many relationship, its now a many-to-many. The tables affected are at the very heart of the application, so its going to be a pain to change. Is that bad architecture? The requirements genuinely did change, in a way that the non IT staff didn't anticipate.
On the other hand there are plenty of times when I can see a quick hack that my team leader suggests will lead to a tangled mess a couple of months down the line. Basically when the application layer is compensating for a crap database design, then its going to cause problems.