title: Multiple or Single BLE Services
body: <p>What, if any, is the value of having multiple BLE <code>services</code>? Versus just throwing all of the <code>characteristics</code> in one single service?</p>
  
  <p>I'm building a BLE interface from a (peripheral) device of our own making. I'm using the <code>STMicro BlueNRG-ms</code> chip. My first prototype has employed 9 <code>characteristics</code>, nicely organized in 4 <code>services</code>. Writing the app side of it now, I'm finding that the separate services just create more <code>UUID</code>s that I have to map, and don't really seem to add any value. The 9 characteristics are all unique, so I don't get any real needed namespacing out of the separate services.</p>