Thursday, January 19, 2012

Title Distributed Design By Kenneth A Brewer © 11/11/2011

Present a 2-3 page presentation of some key features of what should be found within a distributed computing configuration to the Washington DC Consulting team.

The premise of an IT distributed design is to implement a logical organization through automation and process. The design must allow Value, Responsibility, and Growth potentials along with experience in design development deployment and service.
Proper architecture pattern design is among the key features in development of any distributed computing design. The rapid success by its nature, sophisticated systems have grown from independent creativity of applications to Internet-connected networks of numerous network types and managed services, now known as the cloud.
The creation of successful distributed systems will involve how the architecture design would address its accountings within the design its development; how it will be maintained, supported, and governed.
Sophisticated distributed systems will involve these capabilities.
Implementation of applications and or services.
The physical applications will include Communications equipment and wiring Computers, laptops, and similar devices along with backups and archives of sensitive data such as personnel and legal records
Use of services from within as well as external.
Passwords, configuration utilities, confidentiality, and data integrity.
Management of services including risk management
Unauthorized deletion or modification Unauthorized disclosure of information
Database penetration from Hackers, Malware, Trojans, Viruses, and Worms.
Bugs in software Apps
Physical normality’s; floods, earthquakes and human interventions.
Organizations will manage applying methods, patterns, and technologies to model systems which enable proper control.
The scalability is important to any system. Expandability should be incorporated into the design as well. The Government and Companies will not stay the same size; they expand and shrink at any given notice.
Adopting a design is a daunting tasks within tis self. It is important to adopt the working patterns of the environment to which it will be deployed. The architecture will include Key Architectural Styling; Layered, Object-based, Data-centered, and Event-based architectures. (Andrew Tanenbaum, 2007)
Distribution systems consist of internal components such as computers. Computers that can distribute information within the confines of a facility, commonly manufacture, business office, Colleges or Government Campuses. It will consist of a collection of independently working computers which characterization will represent a single functioning operating system. One trunk with many branches many roots all functioning to support the trunk. The distribution system therefore would be classified and named “Tree”.    
The importance or characterization function of any system would show a collaboration known as a relationship between more than one computer including a server and autonomous devices. Devices sometimes called nodes are inline servers making up an array of sensor networks within the main works of the system. Still a mainframe of the system will make up the concentration center of any network. The usefulness of nodes within the network will take care of localized information traffic help distribute the work load thus supporting the mainframe relieving it from over tasking.
 Here is an example: Large corporate companies and the Government will have one or two sites that will support a mainframe. The nodes would be at local sites supporting within that site. A distribution Pipe line as we call it will send information to the main site where IT and it support teams is located. Information can be sent with constancy or updated on a time schedule. This frees up the mainframe from being over tasked and any given moment allowing the steady controlled digestion rate of information to be handled.
Naturally the importance of security cost and monitoring of a system must be considered in its development focusing on numerous aspects that can be followed in order to protect Government proprietary policies.
Firstly taking a look at the assets and level of protection needed evaluating the risk to each asset. Then taking a look at the cost evaluation verses the level of need to protect against threats.
Keep in mind protection is present when human intervention is observed policy is up held. There are too many time is information is lost when a PC is left unattended or on lookers observe what they shouldn’t have.
Generalizing in a key focus important issues, is the exploring the possibilities of compromise, which is called risk assessment. Risk management may include devising the plan, implementing policy and deployment to include deployment planning and most of all training and following up with scheduled training.  
 A conclusion with thought; A distribution system can work over an Intranet, L A N, W A N, local and world over incorporating application layers; User-interface, processing, and data handling. They are capable of being both centralized, and global. Information must be easily read, stored, managed and shared. (Andrew Tanenbaum, 2007) They must be empowered to change, share and be controlled. Attributes must include well maintained balance connectivity with complexity and dissimilar networks systems and devices throughout a managed controlled automation.


Microsoft Support, Revision: 5.4. (2006, Febuary 4). (Microsoft, Producer, & Microsoft ) Retrieved July 4 , 2011, from Microsoft Support:
Internet Protocol Suite. (2011). Retrieved April 16, 2011, from
Andrew Tanenbaum, M. V. (2007). Distributed Systems. Upper Saddle River, NJ, USA: Pearson Prentice Hall.
Benson, C. (2011). Best Practices for Enterprise Security . (G. Berg, Editor, I. C. Ltd, Producer, & Microsoft ) Retrieved 11 09, 2011, from MS Tech Net:
Erbschloe, M. (NOV-2004). Physical Security for IT. In M. Erbschloe, Physical Security for IT. Washington, DC: DIGITAL PRESS.

No comments:

Post a Comment