Supercharging Re-use with the Infrastructure Software Pattern

Composable software patterns promote rapid development of concurrent applications through efficient re-use of complex application infrastructure logic. The idea of a software pattern has been around for some time now. Such a pattern captures a general, repeatable solution to a commonly occurring problem.

Efficient and secure means of describing patterns promotes the development of a large repository from which common classes of problems can be solved without resorting to reinventing the wheel. This involves locating the appropriate pattern for the problem and resolving the specifics for that problem.

Infrastructure (communication, synchronization and arbitration logic) captured in blueprints can also be re-used. The same co-ordination logic can be found solving problems across a wide range of applications and this makes the notion of an infrastructure pattern particularly attractive.

Typically, an infrastructure pattern will describe all the co-ordination logic required to solve a class of problem but leave the actual processing and data descriptions unresolved. The software architect wishing to use the pattern does so by deriving and resolving to specify the appropriate processing and data for the specific task.

An infrastructure pattern can be distributed in a library. The library may be secured so that all of the co-ordination logic not required to be visible in order to use it, is hidden from the user. This protects the IP of the pattern supplier and promotes commercial pattern development, which in turn increases the size of the global pattern resource.

Follow this link to learn more about software blueprinting integral to the infrastructure software pattern.