Architecture?
Architecture. Seems like a funny word when you look at it. A few definitions as follows;
Definitions of
architecture on the Web:
- the discipline dealing with the principles of design and construction
- computer architecture: (computer science) the structure and organization of a computer's hardware or system software; "the architecture of a computer's system software"
wordnet.princeton.edu/perl/webwn
Architecture (from Latin, architectura and ultimately from Greek, "a master builder", from αρχι- "chiefs, leader" , "builder, carpenter") is the art and science of designing buildings and structures.
en.wikipedia.org/wiki/Architecture
We are all pretty familiar with the meaning of the word right. However, many times (more often than not unfortunately) we neglect to consider the importance of this word in relation to the realm of our computer environments. If we were all to be honest we would say that many times the architecting of the proper solution for a project or upgrade are often pushed past in order to meet deadlines or to save money. I'm sure that we would all desire for that to be different. What DBA wouldn't? Ultimately it is those poorly architected solutions that end up getting us called at 3:00 in the morning or in the middle of our childrens birthday party. Not a one of us truly desires for things to be that way. So, with all that being said, why do we? In thinking about some recent experiences, I have asked myself that same question. I am being paid as a professional to offer the best solution for a company so that they can provide the best service for the customer as possible. Right? Right! So why don't I? Ultimately I am responsible to.
Consider this same idea in relation to building a new house. You would go out and find the best architect that you could so that when the winds come up and the storms blow your house is going to stand firm. Your not going to allow for someone half rate so that you can save a few dollars knowing that he is going to allow for some builder to come in and bowl him over everytime he wants to change the plans. You wouldn't allow for a poorly designed foundation to be put in place only to have your beautiful new house built on top of it. Of course no one in their right mind would do that. So, the same should be true when it comes to the area of work, specifically our area of expertise in the DBA world. It is our responsibility to share with managment the changes that need to be made in order for them to have a succesful foundation, a succesful architecture, one that is going to carry them through peak times and provide them with opportunity for growth. I completely understand that money is always an object but part of our job is to sell management on what is right. If they are not willing to buy then we can accept that but we still need to warn them of the ramifications, if for no other reason so that they might listen in the future (not so you can say I told you so).
I don't know, maybe it is because I am getting older and I have been given a bit more liberty to speak my mind these days but, we need to have the determination to do what is right when it comes to architecting solutions for the company we work for. The company that is going to survive is the company that is going to want to grow in the proper direction. The DBA that is going to survive is the one that is willing to get dirty a little in order to drive the company in the direction the need to go in order to survive.
Does this all make sense? Be encouraged, and go architecting your environment today. You'll sleep better tonight and all the nights after if you do!