# Best simple architecture

**URL:** <https://community.amazonquick.com/t/best-simple-architecture/8542>\
**Category:** Q&A\
**Tags:** data-source, quick-sight\
**Created:** [December 16, 2022, 6:19pm UTC](https://community.amazonquick.com/t/best-simple-architecture/8542 "2022-12-16T18:19:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![woliveiras](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/woliveiras/32/3080_2.png) [@woliveiras](https://community.amazonquick.com/u/woliveiras)\
**Post date:** [December 16, 2022, 6:19pm UTC](https://community.amazonquick.com/t/best-simple-architecture/8542/1 "2022-12-16T18:19:02Z")

</div>

Hi everyone, I don’t know if this is the best place to ask about architecture (considering AWS Quick Sight), but… I only have one data source to use, and I’m wondering which case I need to use Data Catalog and AWS Athena. I see no reason for that. Any suggestion?

My AWS Quick Sight can read my data directly from S3. Am I right?

 ![image](https://d1wl4jav5dp96l.cloudfront.net/original/2X/6/699750ca6bdb0de8c036d2f3bcdab3b4e4ba2e6a.png)

---

<div class="post-metadata">

**Author:** ![Max](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/max/32/2288_2.png) [@Max](https://community.amazonquick.com/u/Max)\
**Post date:** [December 16, 2022, 7:28pm UTC](https://community.amazonquick.com/t/best-simple-architecture/8542/2 "2022-12-16T19:28:15Z")

</div>

Yes I can read directly from S3.

However, Athena gives you a lot more depending on your needs.

A couples reasons why we use it:

1. Unstructured data in s3 (Athena allows us to query it and normalize it)
2. Joining data across buckets / folders (data lake)
3. Partitioning data for faster / less data scanned

Those are a couple of the main reasons that came to the top of my mind.

Let me know if that helps!

---

<div class="post-metadata">

**Author:** ![woliveiras](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/woliveiras/32/3080_2.png) [@woliveiras](https://community.amazonquick.com/u/woliveiras)\
**Post date:** [December 16, 2022, 8:04pm UTC](https://community.amazonquick.com/t/best-simple-architecture/8542/3 "2022-12-16T20:04:48Z")

</div>

Hi @Max ,  
Thank you for your quick reply.  
Yes, it was beneficial. I understood the perspective and possibilities to connect different types of data. At the same time, it is interesting the partitioning part.  
I do not sure if I need it in my architecture. My entire data is structured data and comes from a unique data source. If I am not wrong, AWS Athena is more useful in a data lake with a variety type of objects.

Considering my environment and your couples reasons, I have:

1. Unstructured data - It is not my case, my entire data is structured
2. Joining data across buckets - I have just one bucket
3. Partitioning data - I can partition the data (with AWS Glue) and make it available in S3 by querying.

Thank you.