needs to be aware of message loss, producers and consumers always online 5 Message queues • Asynchronous point-to-point communication • Lightweight buffer for temporary storage • Messages stored on Effective failure handling, crashes or disconnects • Broker responsible for message durability • Asynchronous communication, i.e. producer only needs to receive ack from broker 9 Communication patterns Space Decoupling Time Decoupling Synchronization Decoupling Message-passing RPC/RMI Asynchronous RPC Futures Message Queues Pub/Sub Yes Yes Yes Can you fill this in? 19 Pub/Sub vs. other

guest OS. In addition, VirtualBox fully supports asynchronous I/O for its virtual SATA, SCSI and SAS controllers through multiple I/O threads. Since asynchronous I/O is not supported by IDE controllers, for DmiChassisType (bug #11832) • Storage: fixed lost writes if iSCSI is used with snapshots and asynchronous I/O (bug #11479) • Storage: fixed accessing certain VHDX images created by Windows 8 (bug #11502) keyboard: Korean keyboard workaround (bug #11150) • Storage: fixed hang with QCOW images and asynchronous I/O enabled • Storage: fixed hang with newer VHD images (bug #11279) • Storage: actually write

guest OS. In addition, VirtualBox fully supports asynchronous I/O for its virtual SATA, SCSI and SAS controllers through multiple I/O threads. Since asynchronous I/O is not supported by IDE controllers, for DmiChassisType (bug #11832) • Storage: fixed lost writes if iSCSI is used with snapshots and asynchronous I/O (bug #11479) • Storage: fixed accessing certain VHDX images created by Windows 8 (bug #11502) keyboard: Korean keyboard workaround (bug #11150) • Storage: fixed hang with QCOW images and asynchronous I/O enabled • Storage: fixed hang with newer VHD images (bug #11279) • Storage: actually write

guest OS. In addition, VirtualBox fully supports asynchronous I/O for its virtual SATA, SCSI and SAS controllers through multiple I/O threads. Since asynchronous I/O is not supported by IDE controllers, for DmiChassisType (bug #11832) • Storage: fixed lost writes if iSCSI is used with snapshots and asynchronous I/O (bug #11479) 225 15 Change log • Storage: fixed accessing certain VHDX images created by keyboard: Korean keyboard workaround (bug #11150) • Storage: fixed hang with QCOW images and asynchronous I/O enabled • Storage: fixed hang with newer VHD images (bug #11279) • Storage: actually write

guest OS. In addition, VirtualBox fully supports asynchronous I/O for its virtual SATA, SCSI and SAS controllers through multiple I/O threads. Since asynchronous I/O is not supported by IDE controllers, for DmiChassisType (bug #11832) • Storage: fixed lost writes if iSCSI is used with snapshots and asynchronous I/O (bug #11479) • Storage: fixed accessing certain VHDX images created by Windows 8 (bug #11502) keyboard: Korean keyboard workaround (bug #11150) • Storage: fixed hang with QCOW images and asynchronous I/O enabled • Storage: fixed hang with newer VHD images (bug #11279) • Storage: actually write

guest OS. In addition, VirtualBox fully supports asynchronous I/O for its virtual SATA, SCSI and SAS controllers through multiple I/O threads. Since asynchronous I/O is not supported by IDE controllers, for DmiChassisType (bug #11832) • Storage: fixed lost writes if iSCSI is used with snapshots and asynchronous I/O (bug #11479) • Storage: fixed accessing certain VHDX images created by Windows 8 (bug #11502) keyboard: Korean keyboard workaround (bug #11150) • Storage: fixed hang with QCOW images and asynchronous I/O enabled • Storage: fixed hang with newer VHD images (bug #11279) • Storage: actually write

guest OS. In addition, VirtualBox fully supports asynchronous I/O for its virtual SATA, SCSI and SAS controllers through multiple I/O threads. Since asynchronous I/O is not supported by IDE controllers, for DmiChassisType (bug #11832) • Storage: fixed lost writes if iSCSI is used with snapshots and asynchronous I/O (bug #11479) • Storage: fixed accessing certain VHDX images created by Windows 8 (bug #11502) keyboard: Korean keyboard workaround (bug #11150) • Storage: fixed hang with QCOW images and asynchronous I/O enabled • Storage: fixed hang with newer VHD images (bug #11279) • Storage: actually write

guest OS. In addition, VirtualBox fully supports asynchronous I/O for its virtual SATA, SCSI and SAS controllers through multiple I/O threads. Since asynchronous I/O is not supported by IDE controllers, for DmiChassisType (bug #11832) • Storage: fixed lost writes if iSCSI is used with snapshots and asynchronous I/O (bug #11479) • Storage: fixed accessing certain VHDX images created by Windows 8 (bug #11502) keyboard: Korean keyboard workaround (bug #11150) • Storage: fixed hang with QCOW images and asynchronous I/O enabled • Storage: fixed hang with newer VHD images (bug #11279) • Storage: actually write

guest OS. In addition, VirtualBox fully supports asynchronous I/O for its virtual SATA, SCSI and SAS controllers through multiple I/O threads. Since asynchronous I/O is not supported by IDE controllers, for configure DmiChassisType (bug #11832) • Storage: fixed lost writes if iSCSI is used with snapshots and asynchronous I/O (bug #11479) • Storage: fixed accessing certain VHDX images created by Windows 8 (bug #11502) USB keyboard: Korean keyboard workaround (bug #11150) • Storage: fixed hang with QCOW images and asynchronous I/O enabled • Storage: fixed hang with newer VHD images (bug #11279) • Storage: actually write

guest OS. In addition, VirtualBox fully supports asynchronous I/O for its virtual SATA, SCSI and SAS controllers through multiple I/O threads. Since asynchronous I/O is not supported by IDE controllers, for keyboard: Korean keyboard workaround (bug #11150) • Storage: fixed hang with QCOW images and asynchronous I/O enabled • Storage: fixed hang with newer VHD images (bug #11279) • Storage: actually write • Storage: fixed a release assertion in the AHCI emulation when requests where cancelled with asynchronous I/O disabled • Storage: fixed a hang during VM reset under certain circumstances (bug #10898)