title: Runnable vs Service; Lifespan explained with use-cases
body: <p>As I understand - both Runnable and Service are intended to run piece of code in background. My code structure is this:</p>
  
  <ol>
  <li><p>BaseManager.class which is implemented as Singleton and using BaseManager.getInstance() will return single instance in application. Also, when first initialized it automatically creates SmallerAndCompletelyDifferentManager.class - has a dependency.</p></li>
  <li><p>SmallerAndCompletelyDifferentManager.class - creates a Runnable that runs every 2 seconds.</p></li>
  </ol>
  
  <p>Now, I've two scenerios:</p>
  
  <p><strong>SCENERIO A:</strong> I create initialize BaseManager.class in Activity first and use it wherever I need. The Runnable that is inside SmallerAndCompletelyDifferentManager.class runs okay, but as I understand is attached to Activity - if Activity dies, so will the Runnable which I can not afford.</p>
  
  <p><strong>SCENERIO B:</strong> I create a foreground service and initialize BaseManager.class. Does this mean that now the Runnable will work as intended - even if application is in background and Activity has been destroyed?</p>
  
  <p>Am I getting this right or no? The overall plan is to make sure that Runnable survives in background at all costs.</p>