Do you think the problems faced by Hures, both past and present, are unique? Why or why not?
No, because the problems are common in the past and at the present because we realize the problem such as complexity scaling server for example Windows NT server is not scalable also difficult to partition application, dependability for e.g. if the server goes down the whole operation discontinue, PCs must continue to rise and have to be up to date.
Hures compay changed their new client system in 1999 and the company's profit grows but they face the same problem again in few years. To solve this problem they can use the client server architecture that is divided into the categories there are
- File sever
- 1 Tier Architecture
- 2 Tier Architecture
- 3 Tier Architecture
- N-Tire Architecture
In the client/server model, a file server is a computer dependable for the fundamental storage and managing of data files therefore that other computers on the same network can access the files. File servers allow client to share information in excess of network without having to physically transfer files by floppy diskette or various external storage device. Any computer is capable to configure to be a host and act as a file server. Its simplest form, a file server might be typical PC that hold requests for files and post them over the network. In a more difficult network, a file server might be a committed network-attached storage (NAS) device that also serves as a remote hard disk drive for other computers, permit anyone on the network to store files on it as if to their own hard drive.
This software design and develop in 1980's from the file server architecture. The two tire architecture is planned to advance usability by following a forms-based, accessible interface, scalability improves by cooperative up to 100 users, and it also show flexibility by consent to data to be shared. The 2 tier architecture requires least operator connection and commonly used in non-complex, non-time significant information giving out system.
The three-tier software architecture comes out in the 1990s to overcome the margins of the two-tier architecture. The third tire is involving the user interface and the data management components. The three tire architecture is used when an efficient distributed client/server design is need that offer boost performance, elasticity, reusability and scalability while hiding the difficulty of distributed processing on or after the consumer and maintainability,
The 3-tier proxy a few sever call for many SQL queries and renew so it execute much better than 2-tier.
N Tire Architecture
Multi-tier architecture (commonly referred to as n-tier architecture) is a client-server architecture in which, the application processing and the data management are logically separate processes. For example, an application that uses middleware to service data requests between a user and a database provide work for multi-tier architecture. The most general use of "multi-tier architecture" refers to three-tier architecture.
It's debatable what counts as "tiers," but in my opinion it needs to at least cross the process edge or else its called layers. But, it does not need to be in physically different machines
Suggest alternative architectures that could be used to overcome the problems faced by Hures' current Client/Server technology.
CORBA is the independent architecture and associations that computer applications use to work jointly over network. It is support any of the programming languages such as C++ and java. It's also support any computer and operating system.
CORBA is the one of most important improvement in the latest history of information systems. It is design for an emerging technology well-known as distributed object management. CORBA describe a standard framework from which an information system implementer of software developer can simply and speedily combine network software modules and applications to make new and more controlling application. The term CORBA is frequently used to refer to Object Request Broker itself, as well as to the complete OMG architecture.
CORBA is useful in much condition because of the simple way that CORBA integrates machines from so many vendors, with size range from mainframes through minis and desktops to hand-held and place in system; it is the middleware of choice for big enterprises. One of its most essential, as well most frequent, uses is in servers that must hold large number of clients, at high batter rates, with reliability. CORBA works behind the sight in the computer rooms of several of the world's large websites.
Advantages of CORBA
The client does not need to know where an object is physically located.
The client does not know which server hosts an exacting object, and does not mind whether the server is running at the time the client invokes a request.
Client and server can be written in different languages. Its support all language.
A server can use ordinary flat files as its persistent store today and use database tomorrow, without clients ever noticing a difference (other than performance).
Client and server are unaffected by each other's operating system.
Disadvantages of CORBA
No standard to get the initial reference for the naming service.
view as complicated. This is in some parts a injustice, in some parts justificated: remote invocation of CORBA interfaces is at least as simple as over XMLRPC, but the C++ language mapping predates the STL and features three different storage space classes and clumsy handling of sequences.
Firewall unfriendly. There's no real CORBA standard to bind an ORB and its clients to a port or a port range, there are (only) vendor specific options.
One of the suggestions proposed by Hures' IS department is the use of intranet web technology. Examine the pros and cons of such an idea.
An intranet is an internal or limited access network that is like to functionality the same as the internet, however is only offered to within the organization. For example if your organization would like to share particular information like documents, every current announcements, new details etc, but only permit those computers inside the organization entree to this information, you would utilize an intranet. In order to have an intranet, the computers in the network do not have to have a regular internet connection.
Advantages of using the intranet
- Intranet technology can make your company efficient.
- Can increase team productivity, save money, keep employees up-to-date.
- They can be used for lots of things trade with contact. For example it supportive to organization big and small, by give the capability to use intranets as delivery method for application.
- Intranet can help to associates find data fast and simply through a browser interface.
- Workers can easily navigate and access.
- It can shrink the amount of time that it takes to contact an individual.
- Security issues might be the disadvantage with an intranet, because if an employee may have send responsive information for all employee to see.
- Its large amount of information. For example if information excess does exit and can take place when lot of data is up on the intranet. This makes it very tricky for employees to navigate and recover data that is meaningful.
- Limitation of access
- Hidden or unknown complexity and costs
- Management fears loss of control
Do you think the popularity of intranet software and the Internet pose pressure to traditional Client/Server systems?
Not really, because the intranet and internet is not real client sever their part of the client server. Internet and Intranet is access via web browser over the network (it's called web application). Web applications are fashionable due to the ubiquity of web browsers, and the ease of using a web browser as a client, sometimes called a thin client. The capability to update and maintain web applications without distributing and installing software on potentially thousands of client computers is a main reason for their popularity. Frequent web applications include webmail, online trade transaction, online sale and many other functions.
In previous types of client-server computing, every application had its own client program which supply as its user interface and had to be individually installed on each user's individual computer. A promote to the server part of the application would naturally need an upgrade to the clients installed on each user workstation, adding up to the support cost and decrease productivity.
In contrast, web applications use web documents written in a standard format such as HTML (and more recently XHTML), which are supported by a multiplicity of web browsers.