Design Patterns in the JDK

Design Patterns in the JDK, more, more.

Comparing Two High-Performance I/O Design Patterns

Comparing Two High-Performance I/O Design Patterns:
1. Short and clear comparison of Reactor and Proactor I/O patterns.
2. Interesting info about props of different I/O mechanizm on different platforms (Win, Linux, BSD, Solaris).

Summary
This article investigates and compares different design patterns of high performance TCP-based servers. In addition to existing approaches, it proposes a scalable single-codebase, multi-platform solution (with code examples) and describes its fine-tuning on different platforms. It also compares performance of Java, C# and C++ implementations of proposed and existing solutions.

Some cache patterns and terms

From here:

Patterns:
------------------------
Read-Through Caching (синхронное чтение из backing store)
Write-Through Caching (синхронное сохранение в backing store)
Write-Behind Caching (асинхронное сохранение в backing store с возможностью Write-coalescing и Write-combining)
Refresh-Ahead Caching (асинхронная подкачка из backing store)
------------------------

Terms:
-------------
Cache-aside. Означает не более чем то, что время загрузки, обновления, удаления, сохранения сущностей выбираем мы сами. При Read-Through/Write-Through/Write-Behind/Refresh-Ahead кэш решает когда вызывать.

Write-coalescing:
The writes - which are typically much more expensive operations - are often reduced because multiple changes to the same object within the write-behind interval are "coalesced" and only written once to the underlying datasource ("write-coalescing").

Write-combining:
Additionally, writes to multiple cache entries may be combined into a single database transaction ("write-combining") by using the CacheStore.storeAll() method.

Cluster-durable, Disk-durable.

System of record(SoR), more here.

Extract, transform, load(ELF).
------------------------

P.S. Последние два термина(SoR, ELF) - скорее область Data Warehouse но хороший кластерный транзакционный кэш зачастую выполняет часть функций DW.

PJP: GRASP Patterns: Pure Fabrication

GRASP(General Responsibility Assignment Software Patterns) patterns described by Craig Larman in his book:
Applying UML and Patterns, 3ed.
Применение UML 2.0 и шаблонов проектирования
Книгу я бы не советовал читать, вода для будущих менеджеров. И паттерны там не кодирования, а распределения ролей:

• Information Expert
• Creator
• Controller
• Low Coupling
• High Cohesion
• Polymorphism
• Pure Fabrication
• Indirection
• Protected Variations

Но вот термин хороший - Pure Fabrication (Читая Синтетика), хорошее название для классов типа WritePermission, TransactionManager, PriorityInverter. Короче говоря, для антонима Entity. Класс не имеющий никакого двойника в реальном мире.