title: What are the differences between Object Storages for example S3 and a columnar based Technology
body: <p>I was thinking about the difference between those two approches.</p>
  <p>Imagine you must handle information about pattern calls, which later should be
  displayed to the user. A pattern call is a tuple consisting of a unique integer
  identifier (&quot;id&quot;), a user defined name (“name&quot;), a project relative path to the so
  called pattern file (&quot;patternFile&quot;) and a convenience flag, which states whether
  the pattern should be called or not called. And the number of tuples are not known before and they won't be modified after initialization.</p>
  <p>I thought that in this case a column based approach with big query for example would be better in terms of I/O and performance as well as the evolution of the schema. But actually I can't understand why. I would appreciate any help.</p>