An Application as multiple interacting Executables - Dr James Powell(JDP Science Ltd) - GDevCon#4

It is standard to create an Application as a single monolithic Executable. However, there are many use cases that are better served with multiple executables that interact (a more “microservices” style). Use cases include having a Remote UI, or a “Watchdog” EXE that monitors the main exe and restarts it if needed, or a “Tester” EXE that puts another EXE through a series of tests, or an EXE that connects to hardware shared between multiple Applications or that has unique requirements, such as running on a separate computer or in a different bitness of LabVIEW. To really take advantage of these possibilities requires that network communication be easy. I will demonstrate how that can be achieved, specifically using the TCP communication features of Messenger Library. I will also discuss design principles, such as messaging patterns and client-server architecture, that support doing this more generally.
Originally from Canada, James Powell was introduced to LabVIEW while working as a Nuclear Physicist at Lawrence Berkeley National Lab in California. He is now a consultant doing LabVIEW full time and working for a range of technology-focused small companies near Oxford in the UK. He is the author of a number of freely-available packages for LabVIEW, including SQLite Library, JSONtext, Flatline Controls, and Messenger Library
www.gdevcon.com
Follow us on Social Media
Flickr: www.flickr.com...
Instagram: / gdevcon
Facebook: / gdevcon
LinkedIn: / gdev. .
Twitter: / gdevconference
Video Copyright (c) Louis James-Parker (All rights reserved). Use is granted to GDevCon Limited under license.
#LabVIEW #GDevCon #SoftwareDesign