1

 
2  
3  
Recommend projecting this on a whiteboard if possible.
Review application flow, get agreement from class that they could get high-level
diagrams like this from their Apps teams.
Work with the students to identify EPG’s & contracts.
In general, we can identify an EPG when:
-  The group gets the same services from the network, and
-  There are no network services between the groups. That is, devices in each group
are free to communicate with each other.
So the EPG’s should be:
-  Presentation Tier
-  Midrange/Unix System
-  Image Indexing & Image Storage (no filter between these groups)
-  AAA System should be an EPG as well. This is a good opportunity to discuss
shared services.
-  And you could make a case that the doctor’s device is part of the Presentation Tier
VM, because there’s no filtering. But there should be some kind on network service
diagrammed there.

For example a doctor may access an MRI on a tablet while consulting with a patient.
The process, from entering the patient information to receiving the image may
complete in seconds. On the back-end a web based portal provides the search form,
passing the doctor’s credentials and the patient identification to an authorization

4  
Network services are provided as service graphs called by the contracts between the
EPG’s.

5  
6  
7  
8  
Representational state transfer (REST), which is used by browsers, can be thought of
as the language of the Internet. Now that cloud usage is on the rise, various
application programming interfaces (APIs) are emerging to expose Web services and
REST is a logical choice for building APIs that allow end users to connect and interact
with cloud services.

A RESTful API is an application program interface (API) that uses HTTP requests to
GET, PUT, POST and DELETE data.

RESTful APIs explicitly take advantage of HTTP methodologies defined by the RFC
2616 protocol. They simply use "PUT" to change the state of or update a resource,
which can be an object, file or block; "GET" to retrieve a resource; POST" to create
that resource; and "DELETE" to remove it.

9  
10  
11  
12  
13  
14  
15  
h-p://datacenter.github.io/acitoolkit/  provides  be-er  documentaCon,  more  clarity  
for  n00bs.  
 

16  
17  
18  
19  
20  
21  
22  
23