Gain insights into software design patterns in C, explore their implementation, discover underlying principles, and learn to build a vocabulary for better communication and coding practices.

c.tar.gz

main+customer.c

main+customer.c-copy

watches

customers

observer

Reactor

Reactor-copy

observer-copy

Software design patterns are a valuable tool in any software developer's skill set. However, most design patterns are described in the context of an object-oriented programming language such as C++ or Java. The C language is sadly absent in the pattern literature. This course is here to change that by demonstrating that it is possible to use patterns in C programs and how it adds benefits to C programmers. You will learn why design patterns are more of a communication tool than technical solutions, and how patterns let you build and share a common vocabulary that simplifies communication.

The course presents a number of patterns and explains how to implement them in C. Each pattern is introduced via the problem it solves and the domains where the pattern can be used. We also discuss the underlying design principles as well as the trade-offs when applying the pattern. Finally, the course covers a set of coding idioms that will guide you when applying design patterns in C.

Software Design Patterns in C

The Reactor is a pattern for synchronous I/O.

The Reactor is a pattern for synchronous I/O.

 One benefit of learning how to implement an Observer is that the same implementation strategy applies when implementing a Reactor.

One benefit of learning how to implement an Observer is that the same implementation strategy applies when implementing a Reactor.

An Observer means one-to-many notifications, while a Reactor has a one-to-one notification of a specific event handler.

Both Observer and a Reactor have one-to-many notifications, but it’s never a problem to deregister during an event notification in a Reactor.

Since Reactor is an architectural pattern, its notification mechanism always crosses architectural layers.

While the implementation techniques and level of indirection look similar, there's a fundamental difference between the notification mechanism of OBSERVER versus REACTOR:

While the implementation techniques and level of indirection look similar, there’s a fundamental difference between the notification mechanism of OBSERVER versus REACTOR:

The Reactor pattern simplifies event-driven applications by decoupling the different responsibilities?

The Reactor pattern simplifies event-driven applications by decoupling the different responsibilities?

The event polling mechanism can be implemented in either standard C using the socket implementation from the standard library or using platform-specific optimized network routines.

Event notifications can be either a single event notification, or a notification of multiple events using a multi-method interface. 

A Reactor has to violate either the single responsibility principle or the open-closed principle, and it's a trade-off that we need to make when applying the pattern.

Reactor has several possible variations, all depending on the needs of the application. Which of the following represent possible options?

Reactor has several possible variations, all depending on the needs of the application. Which of the following represent possible options?

Test your knowledge of the reactor pattern concepts with this quiz.



Quiz: The Reactor Pattern


Test your knowledge of the reactor pattern concepts with this quiz.

Introduction to Pattern in C

The First-Class ADT Pattern

The State Pattern

The Strategy Pattern

The Observer Pattern

The Reactor Pattern

Idiomatic Expressions

Conclusion

Quiz: The Reactor Pattern