Answers.Body: <p>I don't think you're missing anything, structures are the better channels!</p>
  
  <p>... but things like selecting an entry's parent can contribute to the client's confusion. And that even more in case it doesn't make any sense in the context.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-01T12:56:16.547Z
Answers.LastActivityDate: 2015-04-01T12:56:16.547Z
Answers.UserDisplayName: carlcs
Answers.Body: <p>From the <a href="http://buildwithcraft.com/docs/sections-and-entries#section-types" rel="nofollow noreferrer">official docs</a>:</p>
  <blockquote>
  <p>Channels are used for streams of similar content</p>
  <p>Structures are good for times when you need to store multiple similar entries, and they need to be sorted into a specific order. They can also be hierarchical.</p>
  </blockquote>
  <p>As per your question there's no performance overhead involved, but as a general rule it's usually a good idea to keep things as simple as possible.</p>
  <p>Channels are bit simpler than Structures and if the content is neither hierarchical nor multi-level, there's no reason to use the latter. A <em>blog</em> is a good example of an appropriate use case for a Channel.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-01T17:58:02.490Z
Answers.Text: If there's no need for a Structure, use a Channel. Not for performance reasons, but for UX reasons. Only use a Structure if your entries need to be **nested** or need to be **in a specific order**. If your entries don't need to be nested or ordered, use a Channel.
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-06T17:24:47.707Z
Answers.Text: That's what I thought. Thanks guys for the feedback.
Answers.UserDisplayName: RhealPoirier
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-01T13:04:31.717Z
Answers.LastActivityDate: 2015-09-11T07:06:11.077Z
Answers.LastEditDate: 2020-06-17T08:56:27.903Z
Answers.UserDisplayName: Mats Mikkel Rummelhoff
Body: <p>I can sort structures alphabetically, by date or by specific field. Structures also allow me to sort by the order specified in the Control Panel. So what is the use case for using Channels instead of Structures? Is there a performance cost? Is there anything that I'm missing?</p>
  
Tags: <templating><sections>
Title: Why would I choose Channels as opposed to Structures
ThreadText: # Why would I choose Channels as opposed to Structures
  
  (Asked by: username_0 on 2015-04-01)
  
  I can sort structures alphabetically, by date or by specific field. Structures also allow me to sort by the order specified in the Control Panel. So what is the use case for using Channels instead of Structures? Is there a performance cost? Is there anything that I'm missing?
  
  **Tags:** templating, sections
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2015-04-01. Score: 6 | Accepted answer
  
  From the [official docs](http://buildwithcraft.com/docs/sections-and-entries#section-types):
  
  > Channels are used for streams of similar content
  >
  > Structures are good for times when you need to store multiple similar entries, and they need to be sorted into a specific order. They can also be hierarchical.
  
  As per your question there's no performance overhead involved, but as a general rule it's usually a good idea to keep things as simple as possible.
  
  Channels are bit simpler than Structures and if the content is neither hierarchical nor multi-level, there's no reason to use the latter. A *blog* is a good example of an appropriate use case for a Channel.
  
  > **Comments:**
  > **username_3**: If there's no need for a Structure, use a Channel. Not for performance reasons, but for UX reasons. Only use a Structure if your entries need to be **nested** or need to be **in a specific order**. If your entries don't need to be nested or ordered, use a Channel.  
  > **username_0**: That's what I thought. Thanks guys for the feedback.  
  
  ---
  
  ### Answer by username_1 on 2015-04-01. Score: 1
  
  I don't think you're missing anything, structures are the better channels!
  
  ... but things like selecting an entry's parent can contribute to the client's confusion. And that even more in case it doesn't make any sense in the context.
  
  
  ---
  
  