Focus your design effort on the highest level business logic and unique requirements. 'Patterns' are a trap. Specifically, if you have some message coming in on your port, Your design will consist of a description of that message, and the action taken. Whether your code 'Polls' or uses 'Events' is irrelevant to this design. At one layer or another we are ALWAYS polling: These are your options: Write code that 'polls'. Use a library that polls on another thread and raises an event to your code. Use a library that uses lower level hardware that polls at an embedded level. Use a library, that uses hardware, that uses a chip that raises an interrupt as a result of the microprocessor 'polling' pins very quickly. If your highest level design is agnostic of 'design' patterns, then it is done right. It can be implemented successfully by any combination of language, or 'pattern'

You have a mind like a sieve for facts, just Like Einstein. when you programmed a Z80 with Op Codes, you had them memorized. Back then, you were a 'programmer'. Then came 5 volume Turbo-pascal API for windows 3.1.. The first of many bloated APIs and Dozens of languages ;C++, C, Java, C#, Ruby, Python, Go, Node.js All the meaningless details and irrelevant syntax has been discarded by your brain. You have distilled out an understanding of software structure and design common to all architectures. You now float above most humans like a zen-guru. Your code requires a function pointer ? How that is done exactly, is a job for google, and the auto-complete of whatever IDE you happen to be using. Details like that are for code-monkeys and programmers. not you. your mind contains the pure design, The Plot of the story; The essence of the characters. Language is irrelevant now.. you have become a Software engineer.