Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
30 Cards in this Set
- Front
- Back
|
Scalability dimensions |
- System size - Geographic - Administrative |
|
|
Transparency |
Transparency refers viewing a distributed system as a single entity. |
|
|
Middleware |
It sits between the applications and underlying operating systems Applications interface with the middleware only, and thus they do not need to take into account different types of operating systems and hardware in use |
|
|
Remote Procedure Call Call Semantics |
- Maybe - At-least-one - At-most-one |
|
|
Difference between RPC & RMI |
RMI has a Servant - an instance of a class that provides the body of a remote object |
|
|
Socket |
IP Address + Port + Protocol |
|
|
Stack |
|
|
|
HaaS |
Hardware as a Service |
|
|
IaaS |
Infrastructure as a Service (Virtual Machines) |
|
|
PaaS |
Platform as a Service (typically including operating system, programming language execution environment, database, and web server) |
|
|
SaaS |
Software as a Service (Dropbox, Google Apps) |
|
|
TCP vs UDP |
UDP - messages may arrive out of order or be lost. TCP has overhead. Uses timeouts and retransmissions. |
|
|
Criticisms of Cloud Computing |
Service Level Agreements - 99.9% service uptime Data may be stored in locations outside of your control Dependence on vendors - Lack of open standards, poor interoperability and portability Dependence on high-bandwidth connections - No connection, no service |
|
|
Unstructured Network |
Popular content is likely to be found, however searches for rare data are unlikely to be successful. Use more CPU & RAM & Network requests because more nodes have to be searched. Example: Bit coin |
|
|
Structured Network |
Pastry... |
|
|
N-tier Architecture |
- Presentation Layer - Business Layer - Data Access Layer |
|
|
Servlet Life-cycle: Step 1 |
A user requests to visit a URL through a web browser (GET/POST) |
|
|
Servlet Life-cycle: Step 2 |
A web container receives the HTTP request and maps it to a Servlet |
|
|
Servlet Life-cycle: Step 3 |
The Servlet class is dynamically retrieved and loaded into the memory |
|
|
Servlet Life-cycle: Step 4 |
The web container invokes the Servlet’s constructor, and allocates a Thread |
|
|
Servlet Life-cycle: Step 5 |
The web container invokes the Servlet’s init() and service() methods |
|
|
Servlet Life-cycle: Step 6 |
The Servlet handles the request with doGet(), doPost(), etc. |
|
|
Servlet Life-cycle: Step 7 |
The web container invokes the Servlet’s destroy() method |
|
|
What is WCF? |
A Framework for building service-orientedapplications. |
|
|
WCF Address |
Every WCF service is associated with a uniqueaddress – The location of the service – The transport protocol used to communicate with theservice [transport]://[machine][:port]/[URI] |
|
|
WCF Binding |
The binding specifies how to communicate with the endpoint. - The transport protocol to use (for example, TCP or HTTP). - The encoding to use for the messages (for example, text or binary). - The necessary security requirements (for example, SSL or SOAP message security). |
|
|
WCF Contracts |
- What operations can be called by a client. - The form of the message. - The type of input parameters or data required to call the operation. - What type of processing or response message the client can expect. |
|
|
SOAP stands for |
Simple Object Access Protocol |
|
|
SOAP Messages (4 segments) |
XML document with four possible segments Envelope – Denotes that the message is SOAP, and where the SOAPmessage starts and ends Header – An optional header which contains application specificinformation Body– The main body of the SOAP message Fault– Optional error codes and status information |
|
|
WSDL |
Web Service Description Language |
