Primary Task Response: Within the Discussion Board area, write 500–700 words tha

Question

Primary Task Response: Within the Discussion Board area, write 500–700 words that respond to the following questions with your thoughts, ideas, and comments. This will be the foundation for future discussions by your classmates. Be substantive and clear, and use examples to reinforce your ideas. You are the chief financial officer (CFO) of a home health corporation. You have been asked by the board of directors to develop an overview of the cost reimbursement available from private, state, and federal agencies for high-technology home care being delivered to the corporation's current patients. Discuss the following: •Investigate and predict what impact the baby boomers will have on this issue (including the understanding that since 2011 more than 10,000 people are applying for and receiving Medicare each month).

Explanation / Answer

Distributed systems:

All large computer based systems are now distributed systems.
Information processing is distributed over several computers rather than confined to a single machine.
Distributed software engineering is therefore very important for enterprise computing systems.

Here are few characteristics of distributed systems:
1.Resource sharing:It means that distributed systems will share software and hardware resources.
2.Openness:Use of equipment and software from different vendors will tells us that distributed systems shows the quality of openness.
3.Scalability:Increased throughput by adding new resources.
4.Fault tolerance:It is the ability to continue in operation after a fault has occured.
5.Concurrency:Concurrent processing to enhance performance will clearly exhibits the quality of concurrency by distributed systems.

Advantages of distributed systems:
their are many advantages of distributed systems ,some of which are discussed below.
1.In distributed system their is global database administrator for entire system.Apart from the global database administrator,their will be a local database administrator for each site.
2.Autonomy will be provided by the distributed systems.Because of sharing data by means of data distribution each site is able to retain a degree of control over data that are locally stored.
3.Each local database administrator may have different degree of autonomy.
4.Distributed systems allows sharing of data.
5.Availability is also provided by distributed systems.It means that if one site fails in distributed system,the remaining sites may be able to continue in operating.

Disadvantages of distributed systems:
Here are few disadvantages of distributed systems:
1.Security:Distributed systems are more susceptible to externam attacks.So,the security will be less in distributed systems.
2.Unpredictability:Unpredictable responses depending on the system organization and network load will happen in case of distributed systems.
3.Complexity:Distributed systems are more complex while compared to centralised systems.
4.Manageability:In casr of distributed systems,we need more effort for system management.

Architecture of distributed systems:
their are two categories oserver f architectures of distributed systems.They are:
1.Client-server Architecture:Distributed services which are called by clients.Servers that provide services are treated differently from clients that use servers.
2.Distributed object Architecture:No distinction between clients and servers.Any object on the system may provide and use services from other objects.

Fundamental components of a distributed system:
The following are the few fundamental components of distributed system:

1.Discovery:suppose that you have somewhere to deploy, and the ability to deploy, your services need to be able to find each other.
generally anyone will prefer dynamic, logical service discovery where services register their availability and connection information and then everything finds each other via the discovery service.
A lot of people use Zookeeper for this nowadays, and most everyone I know who has used it loves it.
In an ideal world the location of your discovery system is the only well known address in the whole system.
Some things don't participate well in discovery out of the box - those being fully formed components such as databases, caches, and so on.
How you integrate these will vary, but two good techniques are to use of companion processes which interact with the discovery service, and static entries in the discovery service. In the case of a companion process, the companion generally does a very basic health check and provides a local view of whatever is needed from the service. In the case of static entries, the entry may be placed and removed by the startup script, or via some alternate channel.

2.Configuration:In generally, people like immutable configuration obtained at startup or deployment time.
A new set of configs means a restart. In this case, you can either have the deployment system provide it to the application, or have the application itself fetch it.

3.Deployment:The first part of application management is a means of getting application components onto servers and controlling them.
generally prefer deploying complete, singular packages which bundle up all their volatile dependencies. Tools like Galaxy and Cast do this nicely. Think hard about how development, debugging, and general work with these things will go, as being pleasent to work with during dev, test, and downtime will trump idealism in production.

4.Operational Platform:At the very base of the system you need to have networking gear, servers, the means to put operating systems onto the servers, bring them up to baseline configuration, and monitor their operational status (disk, memory, cpu, etc). There are lots of good tools here. Getting the initial bits onto disk will usually be determined by the operating system you are using, but after that Chef or Puppet should become your friend.

5.Application Monitoring:Application level monitoring and operational level monitoring are very similar, and can frequently be combined in one tool, but are conceptually quite different.
For one thing, operational monitoring is usually available out of the box from good old Nagios to newer tools like 'noit.

Generally you will want to track the same kinds of things, but how you get it, and what they mean will vary by the application. Monitoring is a huge topic, go google it.

Related Questions

Navigate

• Browse (All)
• Browse P
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.