Welcome!

Java IoT Authors: Jyoti Bansal, Craig Lowell, Elizabeth White, Carmen Gonzalez, Liz McMillan

Related Topics: Java IoT

Java IoT: Article

Java Basics: Introduction to Java Threads, Part 1

Lesson 8, Java Basics

A program can perform its actions either in a sequence (one after another) or in parallel. In a sequential mode, if a program needs to call two methods of a class, the second method is called after the first one completes. In other words, such programs have only one thread of execution. In some cases, when a second method does not depend on the results of the first one, you can substantially speed up the processing by executing these methods at the same time in a multi-threaded mode.

A good example of a program that creates multiple threads is your Web browser. You can browse the Internet while downloading some files - one program runs two threads of execution. If these two tasks would have run sequentially, the browser's screen would have been frozen until the download is complete. In case of a one-processor computer, each thread gets a slice of the processor's time. Since this happens pretty fast, a user can't notice small delays. If you run a multi-threaded program on a computer that has two or more processors, performance of such program can be increased dramatically.

Multi-threading is used in most of the graphical games: while one thread displays GUI components on the screen, the second thread calculates coordinates of the next image based on the player's move.

A Sample Program Without Threads

When I teach classes, I usually start with some theory and then show sample programs to illustrate the subject, but in this case I believe it's better to start by writing two very simple programs to give you a better feeling of why threads are needed. I'll give you some explanations as we go.

 Each of these sample programs will use Swing components - a button and a text field. When a user hits the button Kill Time, the program starts a loop that increments a counter thirty thousand times. The current value of the variable-counter will be displayed on the title bar of the window. The class NoThreadsSample has only one thread of execution and you won't be able to type anything in the text field until the loop is done. This loop exclusively takes all processor's time, that's why the window is locked.

For those of you who did not have a chance to create GUI screens with Swing, let me just say that the constructor of the class NoThreadsSample creates a button and a text field and registers this class with so called ActionListener that will process button clicks. Whenever a user clicks on the button, JVM will call the method actionPerformed(), and we start our kill-time-loop there. This class is inherited from JFrame that comes with Swing and the ActionListener interface is needed for this program to process clicks on the button.


import javax.swing.*;
import java.awt.GridLayout;
import java.awt.event.ActionListener;
import java.awt.event.ActionEvent;

public class NoThreadsSample extends JFrame implements ActionListener{
  // Constructor
  NoThreadsSample(){
  // Create a frame with a button and a text field
	GridLayout gl =new GridLayout(2,1);
	this.getContentPane().setLayout(gl);
	JButton myButton = new JButton("Kill Time");
	myButton.addActionListener(this);
	this.getContentPane().add(myButton);
	this.getContentPane().add(new JTextField());
  }
  // Process button clicks
  public void actionPerformed(ActionEvent e){
  // Just  kill some time to show
  // that window controls are locked
    	for (int i=0; i<30000;i++){
    	  this.setTitle("i="+i);
    	}
    }

  public static void main(String[] args) {
    // Create an instance of the frame
    NoThreadsSample myWindow = new NoThreadsSample();
    // Ensure that the window can be closed
    // by pressing a little cross in its corner
    myWindow.setDefaultCloseOperation(
	  WindowConstants.EXIT_ON_CLOSE);

    // Set the frame's size - top left corner
    // coordinates, width and height
	myWindow.setBounds(0,0,150, 100);
    //Make the window visible
    myWindow.setVisible(true);
  }
}

Compile and run this class and see for yourself that the window is locked for some time and that you can't use the text field until the loop is over.

Re-writing our Sample Program With Threads

The next version of this little window will create and start a separate thread for the loop, and the main window's thread will allow you to type in the text field.

In Java, you can create a thread using one of the following ways:

1.  Create an instance of the Java class Thread and pass to this instance an object that implements Runnable interface. For example, if a class SomeGameProcessor implements Runnable interface the code may look as follows:


SomeGameProcessor sgp = new SomeGameProcessor();
Thread worker = new Thread(sgp);

The Runnable interface requires that a class has to implement the code that must be running as a separate thread in the method run(). But to start the thread, you have to call the Thread's method start(), that will actually call your method run(). I agree, it's a bit confusing, but this is how you start a thread:


worker.start();

2.  Create a subclass of the class Thread and implement the method run() there. To start the thread call the method start().


public class MyThread extends Thread{

  public static void main(String[] args) {
	MyThread worker = new MyThread();
	worker.start();
  }
  public void run(){
    // your code goes here
  }
}

In my class ThreadsSample I'll create a thread using the first method because this class already extends JFrame, and you can't inherit a Java class from more than one parent.


import javax.swing.*;
import java.awt.GridLayout;
import java.awt.event.ActionListener;
import java.awt.event.ActionEvent;

public class ThreadsSample extends JFrame
             implements ActionListener, Runnable{

  // Constructor
  ThreadsSample(){
   // Create a frame with a button and a text field
	GridLayout gl =new GridLayout(2,1);
	this.getContentPane().setLayout(gl);
	JButton myButton = new JButton("Kill Time");
	myButton.addActionListener(this);
	this.getContentPane().add(myButton);
	this.getContentPane().add(new JTextField());
  }

  public void actionPerformed(ActionEvent e){
  // Create a thread and execute the kill-time-code
  // without blockiing the window
    Thread worker = new Thread(this);
    worker.start();  // this calls the method run()
  }

  public void run(){
  // Just  kill some time to show that
  // window controls are NOT locked
	for (int i=0; i<30000;i++){
  	  this.setTitle("i="+i);
	}
   }

  public static void main(String[] args) {

	ThreadsSample myWindow = new ThreadsSample();
  // Ensure that the window can be closed
  // by pressing a little cross in the corner
  	myWindow.setDefaultCloseOperation(
	       WindowConstants.EXIT_ON_CLOSE);

  // Set the frame's size and make it visible
	myWindow.setBounds(0,0,150, 100);
	myWindow.setVisible(true);
  }
}

The class ThreadsSample starts a new thread in the method actionPerformed(), which is called whenever you click on the button Kill Time. After this, the thread with a loop and the main thread take turns in getting slices of the processor's time. Now you can type in the text field (the main thread), while the other thread runs the loop! Try it out.

After calling the method worker.start(), our program does not wait until the code in the method run() completes, but runs this code in a separate thread of execution. Since the GUI part runs in a different thread, the screen is not locked.

Note - There are special requirements for using Java threads in Swing, and you can find more here: http://java.sun.com/products/jfc/tsc/articles/threads/threads1.html

Sleeping Threads

One of the ways for a tread to step aside and let the processor continue working with other threads is by using the method sleep()of the class Thread. This method takes one parameter that specifies (in milliseconds) how log the thread has to sleep. For example, if your program needs to refresh the screen with stock quotes every five seconds (see an example of how to get stock quotes in the lesson Reading Data from the Internet), you can do it like this:

  public void run(){

  try{
   while (true)
     // call the code that gets the price quote here
     // and display the current price of the stok(s)
     sleep (5000);  // sleep for 5 second
   }
  }catch(InterruptedException e ){
    System.out.println(Thread.currentThread().getName()
	  + e.toString());
  }
}   

In our endless loop this thread will "wake up" every five seconds, execute the code that gets the stock quote and will go to sleep again for another five seconds. The method sleep() may throw the InterruptedException, that's why we handle it in a try/catch block. A thread can be interrupted not only because of an error condition, but a program can try to interrupt a running thread by calling its method interrupt:


worker.interrupt();

How to Stop a Thread

Ideally, a thread should die after completing the code in its method run(). But what if you'd like to stop it earlier? The class Thread has a method stop() that was deprecated a long time ago, because in some cases it was making programs unstable (the methods suspend() and resume() were deprecated as well). I'm not planning to elaborate on this topic here, but you can read about this at the following Web page : java.sun.com/j2se/1.5.0/docs/guide/misc/ threadPrimitiveDeprecation.html.

So, we need to find some other way to stop unwanted threads.

The class ThreadStopSample is a slightly modified version of the class ThreadsSample, and it will show you how to stop a thread by declaring a flag variable and setting it to true when the thread has to be killed. We declare a boolean variable stopThreadFlag and the GUI button will work as a toggle to start or stop the thread. The method actionPerformed(), is called whenever the user clicks on the button, and we check there if the thread is currently running ( the method Thread.isAlive() returns true), and set the stopThreadFlag to true in this case. On the other hand, the code in the method run() is enclosed in the loop while (!stopThreadFlag). As soon as the variable stopThreadFlag is set to true, the loop (read Thread) will end.


import javax.swing.*;
import java.awt.GridLayout;
import java.awt.event.ActionListener;
import java.awt.event.ActionEvent;

public class ThreadStopSample extends JFrame
              implements ActionListener, Runnable{

   private volatile boolean stopThreadFlag = false;
   Thread worker=null ;

    // Constructor
   ThreadStopSample(){
	// Create a frame with a button and a text field
	GridLayout gl =new GridLayout(2,1);
	this.getContentPane().setLayout(gl);
	JButton myButton = new JButton("Start/Stop Thread");
	myButton.addActionListener(this);
	this.getContentPane().add(myButton);
	this.getContentPane().add(new JTextField());
   }

    public void actionPerformed(ActionEvent e){
    	// If the thread is running, turn the flag to stop it.
    	// Otherwise, start the thread
        if (worker!=null && worker.isAlive()){
        	setStopThreadFlag(true);
        }else{
        	setStopThreadFlag(false);
        	worker = new Thread(this);
        	worker.start();  // this calls the method run()
        }

    }

    public void run(){
       // Run the thread until the stop flag is on
       int i=0;
       while (!stopThreadFlag){
		this.setTitle("i="+i);
		i++;
       }
    }

     public void setStopThreadFlag(boolean flag)
    {
    	 stopThreadFlag = flag;
    }

    public static void main(String[] args) {
	// Create an instance of the frame
	ThreadStopSample myWindow = new ThreadStopSample();
	// Ensure that the window can be closed
	// by pressing a little cross in the corner
	myWindow.setDefaultCloseOperation(
	         WindowConstants.EXIT_ON_CLOSE);

	// Set the frame's size ang make it visible
	myWindow.setBounds(0,0,150, 100);
	myWindow.setVisible(true);
   }

}

Please note that the variable stopThreadFlag is declared as volatile. This is done to make sure that if the value of this variable is changed by one of the threads in a multi-threaded application, the running thread will see its latest value. This basically forces JVM to always refresh the local copies of such variables, i.e. in a CPU register

Our method run() just increments the counter, but in real-world applications a running thread may use some other resources, for example work with files, databases, or maintain connections to remote computers. When you stop such thread, make sure that it closes all opened resources - the finally clause of the try block is the right place to do this (see the lessons on working with streams).

Threads are used in most of the Java applications one way or the other. Either your program explicitly creates and handles threads, or an application server where your program may be deployed can create multiple threads without any additional programming required on your part. For example, hundreds of users may work at the same time with an online store that may be implemented as a Web application using Java Servlets. Each user's request will be processed by the same servlet, but the servlet container will create a separate thread of execution for each of these requests.

In this lesson you've learned the basics of threads. In a follow up article I'll show you how to create a more useful multi-threaded program than our kill-time sample.

More Stories By Yakov Fain

Yakov Fain is a Java Champion and a co-founder of the IT consultancy Farata Systems and the product company SuranceBay. He wrote a thousand blogs (http://yakovfain.com) and several books about software development. Yakov authored and co-authored such books as "Angular 2 Development with TypeScript", "Java 24-Hour Trainer", and "Enterprise Web Development". His Twitter tag is @yfain

Comments (7) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
Simon 08/27/04 01:55:16 PM EDT

Jeff, the article states:
"The class NoThreadsSample has only one thread of execution and you won''t be able to type anything in the text field until the loop is done. This loop exclusively takes all processor''s time, that''s why the window is locked"

What happens if I have a 2 CPU box ? One CPU will be 100%, but the other will be 0%, plenty of resource to type in the text field.
The fact that you cannot type in the text field is absolutely not related to the fact that the "loop exclusively takes all processor''s time", but more to Swing''s architecture.
For further info, read the links I gave. They will explain the Swing "freeze" problem (the author refer to it as "the window is locked"), and the Swing architecture as well.

Jeff 08/27/04 01:41:24 PM EDT

Simon, you stated:

"First of all, the single thread rule of Swing is violated (setTitle() is called from outside the event dispatch thread). This is a gross mistake, especially when there is no explanation on why it has been done. Second, it is said that the reason why it is not possible to type in the textfield is that because the CPU is 100% busy. This is clearly false, and shows bad understanding of how Swing works."

Can you please explain your answers here? I''m a noob so saying something is "clearly false" without a "why" doesn''t help me. Thanks!

Simon 08/27/04 09:21:34 AM EDT

Read again - carefully this time - the article you mention, and you''ll see that your example *does* violate the single thread rule.

Also, I suggest you to read the second and third continuations of the same article.
For interested readers, since those resources are not mentioned by your article, here are the links:
http://java.sun.com/products/jfc/tsc/articles/threads/threads1.html
http://java.sun.com/products/jfc/tsc/articles/threads/threads2.html
http://java.sun.com/products/jfc/tsc/articles/threads/threads3.html

Another good reference for Swing threading is this:
http://foxtrot.sourceforge.net/
especially here:
http://foxtrot.sourceforge.net/docs/toc.php

About the catch 22 situation, I would say you shoot in your foot, since 99% of thread tutorials out there do not use Swing as a first thread example, exactly because it requires too much background. Noone forced you to use a wrong example, to talk about wrong problems (the 100% CPU thing) and to suggest wrong solutions for them.

Once more, not good.

It''s just unfortunate that only few readers, after reading the article, take the time to read the comments.

Yakov 08/27/04 06:50:01 AM EDT

1. Calling setTitle() from the actionPerformed is fine and does not violate Swing''s single thread rule because actionPerformed() method is automatically invoked in the dispath-thread (see http://java.sun.com/products/jfc/tsc/articles/threads/threads1.html)

2. I agree that calling another thread from the actionPerformed() should have been done using invokeLater(), but it''s a catch 22 situation: I can''t explain this without explaining thread basics first. Probably I should have mention that Swing has its special way of working with threads.
But again, I just try to explain one Java feature at a time...

Simon 08/27/04 04:36:23 AM EDT

Hi,
while I understand this is a simple example and an introductory article on threads, I am surprised by the errors it contains.
First of all, the single thread rule of Swing is violated (setTitle() is called from outside the event dispatch thread). This is a gross mistake, especially when there is no explanation on why it has been done.
Second, it is said that the reason why it is not possible to type in the textfield is that because the CPU is 100% busy. This is clearly false, and shows bad understanding of how Swing works. Furthermore, it is proposed as a solution to move the code in another thread, which is even worse (see previous point).
Third, it is possible to start more than one worker but the example does not seem to handle this situation.
Fourth, as already noted by Marc, catching an InterruptedException without re-interrupting the current thread is bad practice.

I think stating right things from the beginning, especially if the goal of the article is to be an introduction to threads for people that don''t know them, is a better approach.
Correcting things lately will always be too late, and when people will violate Swing''s single thread rule as a normal coding style, they will always have the justification that they read an article that did so. Not good.

Yakov 08/25/04 04:44:09 PM EDT

Marc,

This is a just a first light intro to threads and my sample code is written properly. At the end of the article I''ve also mentioned that you may need to close all io resources when killing a thread.

Your suggestion with interrupt() may not always work with threads that have opened streams. It''s recommended to stop such threads by simple closing these streams, connections, etc.

Let''s keep things simple for now :)

Marc 08/25/04 03:48:02 PM EDT

If your while loop launches more threads, or does blocking IO operations, the main thread (with the invariant while (!stopThreadFlag)) will end but you still have open resouces and other threads that may still be running.

A better (albeit not as elegant) mechanism to use would be the interrupt() method.

Here is a rewritten version using it. I''m sure this comment box will screw up formatting.

import java.awt.*;
import java.awt.event.*;
import javax.swing.*;

public class ThreadStopSample extends JFrame implements ActionListener, Runnable {

Thread worker = null;

// Constructor
ThreadStopSample() {
// Create a frame with a button and a text field
GridLayout gl = new GridLayout(2, 1);
this.getContentPane().setLayout(gl);
JButton myButton = new JButton("Start/Stop Thread");
myButton.addActionListener(this);
this.getContentPane().add(myButton);
this.getContentPane().add(new JTextField());
}

public void actionPerformed(ActionEvent e) {
if (worker != null && worker.isAlive()) {
worker.interrupt();
} else {
worker = new Thread(this);
worker.start();
}
}

public void run() {
int i = 0;
while (true) {
try {
this.setTitle("i=" + i);
i++;
Thread.sleep(1);
} catch (InterruptedException ie) {
Thread.currentThread().interrupt();
break;
}
}
}

public static void main(String[] args) {
ThreadStopSample myWindow = new ThreadStopSample();
myWindow.setDefaultCloseOperation(WindowConstants.EXIT_ON_CLOSE);
myWindow.setBounds(0, 0, 150, 100);
myWindow.setVisible(true);
}

}

@ThingsExpo Stories
IoT is at the core or many Digital Transformation initiatives with the goal of re-inventing a company's business model. We all agree that collecting relevant IoT data will result in massive amounts of data needing to be stored. However, with the rapid development of IoT devices and ongoing business model transformation, we are not able to predict the volume and growth of IoT data. And with the lack of IoT history, traditional methods of IT and infrastructure planning based on the past do not app...
"LinearHub provides smart video conferencing, which is the Roundee service, and we archive all the video conferences and we also provide the transcript," stated Sunghyuk Kim, CEO of LinearHub, in this SYS-CON.tv interview at @ThingsExpo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
With major technology companies and startups seriously embracing IoT strategies, now is the perfect time to attend @ThingsExpo 2016 in New York. Learn what is going on, contribute to the discussions, and ensure that your enterprise is as "IoT-Ready" as it can be! Internet of @ThingsExpo, taking place June 6-8, 2017, at the Javits Center in New York City, New York, is co-located with 20th Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry p...
The 20th International Cloud Expo has announced that its Call for Papers is open. Cloud Expo, to be held June 6-8, 2017, at the Javits Center in New York City, brings together Cloud Computing, Big Data, Internet of Things, DevOps, Containers, Microservices and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding business opportunity. Submit your speaking proposal ...
"There's a growing demand from users for things to be faster. When you think about all the transactions or interactions users will have with your product and everything that is between those transactions and interactions - what drives us at Catchpoint Systems is the idea to measure that and to analyze it," explained Leo Vasiliou, Director of Web Performance Engineering at Catchpoint Systems, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York Ci...
Discover top technologies and tools all under one roof at April 24–28, 2017, at the Westin San Diego in San Diego, CA. Explore the Mobile Dev + Test and IoT Dev + Test Expo and enjoy all of these unique opportunities: The latest solutions, technologies, and tools in mobile or IoT software development and testing. Meet one-on-one with representatives from some of today's most innovative organizations
20th Cloud Expo, taking place June 6-8, 2017, at the Javits Center in New York City, NY, will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud strategy.
SYS-CON Events announced today that Super Micro Computer, Inc., a global leader in Embedded and IoT solutions, will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 7-9, 2017, at the Javits Center in New York City, NY. Supermicro (NASDAQ: SMCI), the leading innovator in high-performance, high-efficiency server technology, is a premier provider of advanced server Building Block Solutions® for Data Center, Cloud Computing, Enterprise IT, Hadoop/Big Data, HPC and E...
SYS-CON Events announced today that Linux Academy, the foremost online Linux and cloud training platform and community, will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Linux Academy was founded on the belief that providing high-quality, in-depth training should be available at an affordable price. Industry leaders in quality training, provided services, and student certification passes, its goal is to c...
WebRTC is the future of browser-to-browser communications, and continues to make inroads into the traditional, difficult, plug-in web communications world. The 6th WebRTC Summit continues our tradition of delivering the latest and greatest presentations within the world of WebRTC. Topics include voice calling, video chat, P2P file sharing, and use cases that have already leveraged the power and convenience of WebRTC.
WebRTC sits at the intersection between VoIP and the Web. As such, it poses some interesting challenges for those developing services on top of it, but also for those who need to test and monitor these services. In his session at WebRTC Summit, Tsahi Levent-Levi, co-founder of testRTC, reviewed the various challenges posed by WebRTC when it comes to testing and monitoring and on ways to overcome them.
"A lot of times people will come to us and have a very diverse set of requirements or very customized need and we'll help them to implement it in a fashion that you can't just buy off of the shelf," explained Nick Rose, CTO of Enzu, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
Every successful software product evolves from an idea to an enterprise system. Notably, the same way is passed by the product owner's company. In his session at 20th Cloud Expo, Oleg Lola, CEO of MobiDev, will provide a generalized overview of the evolution of a software product, the product owner, the needs that arise at various stages of this process, and the value brought by a software development partner to the product owner as a response to these needs.
WebRTC services have already permeated corporate communications in the form of videoconferencing solutions. However, WebRTC has the potential of going beyond and catalyzing a new class of services providing more than calls with capabilities such as mass-scale real-time media broadcasting, enriched and augmented video, person-to-machine and machine-to-machine communications. In his session at @ThingsExpo, Luis Lopez, CEO of Kurento, introduced the technologies required for implementing these idea...
The WebRTC Summit New York, to be held June 6-8, 2017, at the Javits Center in New York City, NY, announces that its Call for Papers is now open. Topics include all aspects of improving IT delivery by eliminating waste through automated business models leveraging cloud technologies. WebRTC Summit is co-located with 20th International Cloud Expo and @ThingsExpo. WebRTC is the future of browser-to-browser communications, and continues to make inroads into the traditional, difficult, plug-in web co...
The Internet of Things will challenge the status quo of how IT and development organizations operate. Or will it? Certainly the fog layer of IoT requires special insights about data ontology, security and transactional integrity. But the developmental challenges are the same: People, Process and Platform. In his session at @ThingsExpo, Craig Sproule, CEO of Metavine, demonstrated how to move beyond today's coding paradigm and shared the must-have mindsets for removing complexity from the develop...
While not quite mainstream yet, WebRTC is starting to gain ground with Carriers, Enterprises and Independent Software Vendors (ISV’s) alike. WebRTC makes it easy for developers to add audio and video communications into their applications by using Web browsers as their platform. But like any market, every customer engagement has unique requirements, as well as constraints. And of course, one size does not fit all. In her session at WebRTC Summit, Dr. Natasha Tamaskar, Vice President, Head of C...
Who are you? How do you introduce yourself? Do you use a name, or do you greet a friend by the last four digits of his social security number? Assuming you don’t, why are we content to associate our identity with 10 random digits assigned by our phone company? Identity is an issue that affects everyone, but as individuals we don’t spend a lot of time thinking about it. In his session at @ThingsExpo, Ben Klang, Founder & President of Mojo Lingo, discussed the impact of technology on identity. Sho...
DevOps is being widely accepted (if not fully adopted) as essential in enterprise IT. But as Enterprise DevOps gains maturity, expands scope, and increases velocity, the need for data-driven decisions across teams becomes more acute. DevOps teams in any modern business must wrangle the ‘digital exhaust’ from the delivery toolchain, "pervasive" and "cognitive" computing, APIs and services, mobile devices and applications, the Internet of Things, and now even blockchain. In this power panel at @...
With all the incredible momentum behind the Internet of Things (IoT) industry, it is easy to forget that not a single CEO wakes up and wonders if “my IoT is broken.” What they wonder is if they are making the right decisions to do all they can to increase revenue, decrease costs, and improve customer experience – effectively the same challenges they have always had in growing their business. The exciting thing about the IoT industry is now these decisions can be better, faster, and smarter. Now ...