- Why should BOINC use grids
    - Resources in general more secure and owners trusted
       - Can be used for result verification
    - Resources are more stable, available, and often underutilized
       - Easier to support low-latency jobs for example
    - Resources often connected by high bandwidth links
       - Could support data-intensive or data-parallel jobs
    - Environment (in terms of software/libraries) tends to be more homogeneous and configurable
    - Easy to run the BOINC client on a cluster and supercomputers by statically compiling a stand-alone client
       - Examples: condor pools that run BOINC jobs when their machines are not in use
    - Leverage existing grid software
       - Job submission often simpler with web portals
 - Why should grids use BOINC
    - Order of magnitude more computing power and storage at fraction of the cost
    - Many grid jobs are already task parallel,
    - Challenge
       - Lack of mechanisms and standards to allow a job submitted on a grid to run easily in BOINC
          - Cannot rely on the existence of a software stack
          - Concept of an individual user or job (and access rights) in BOINC
          - Credit accounting for these jobs