Distribution Strategies

Question 1

Talk about Distributed Applications

Answer 1

Applications with distributed objects communicate remotely, objects from application design become separate components at implementation, and each is executed on a separate processing node

Question 2

Talk about local interfaces

Answer 2

For local calls, many methods with simple functionality. No problem if many calls are needed (ex: methods to set part of an address)

Question 3

Talk about remote interfaces

Answer 3

For remote calls, complex functionality, maximize number of calls (one method to set an address)

recommendation: minimize remote calls, avoid distributed objects

Question 4

What’s the alternative for remote calls?

Answer 4

Horizontal scalability (many computers with many replicas)
- all application objects are hosted in a single machine, then execute multiple of the app on different machines

Question 5

What are the unavoidable remote calls?

Answer 5

• Between client and server
• Between application server and database
  _ usually there’s separate machines to
  improve performance and shared data
  to avoid synchronization issues
  _ Leverage SQL Remote Interface, well
  prepared to minimize issues due to
  remote calls.

Question 6

Talk about distributed object patterns

Answer 6

• Remote facade: group methods that are called remotely in a single interface. Built on top of simpler local methods
  -Data transfer object: for return calls that receive or return objects, simplified version of the local object that reduces the amount of data sent