cloud database diagrams and SQL vs NoSQL comparison

cloud_analysis/Right_Database.md

@@ -0,0 +1,16 @@
+**Review:**
+
+After going through the cloud database comparisons and the SQL vs NoSQL diagram, I feel like there’s no one-size-fits-all answer when it comes to picking a database. It really depends on what the project needs.
+
+From what I saw:
+
+* SQL options like PostgreSQL or AWS RDS are great when you want strong structure and need to run complex queries, especially when data integrity is super important.  
+* NoSQL ones like Firebase and MongoDB are better when you want to move fast, need flexibility, pluspoint Firebase can use GoogleAuth and you’re handling a lot of user data or something that doesn’t fit neatly into tables.  
+* Supabase kind of feels like a good middle ground – gives you SQL power with some of the ease of Firebase.
+
+What stood out to me is how important scalability, learning curve, and pricing are in real-life use. It’s not just about performance, but also how much time you’ll spend maintaining and tuning stuff.
+
+For me personally, I think using both SQL and NoSQL together can be a smart move. Like maybe SQL for structured things like accounts and payments, and NoSQL for stuff like chat or logs. Depends on the use case.
+
+This comparison really helped me understand what trade-offs exist between the systems and made me think more practically about tech choices.
+

cloud_analysis/SQL vs NoSQL/RvNonR.puml

@@ -0,0 +1,32 @@
+@startuml
+skinparam padding 20
+skinparam backgroundColor #000000
+skinparam shadowing false
+skinparam rectangle {
+  BackgroundColor Black
+  BorderColor White
+  FontColor White
+  RoundCorner 25
+  FontSize 13
+  MinWidth 250
+  MinHeight 250
+}
+
+title "<color:white><size:20><b>SQL vs NoSQL Databases: Pros & Cons</b></size></color>"
+
+' Legend
+rectangle "Legend\n\n+ = Advantage (Pro)\n- = Limitation (Con)" as Legend
+
+' SQL Databases
+rectangle "SQL Databases\n\n+ Strong consistency (ACID compliance)\n+ Well-defined schemas\n+ Complex joins and transactions\n+ Proven reliability and stability\n+ Mature ecosystem and tools\n+ Better for structured data\n+ Standardized query language\n\n\n- Less flexible schema\n- Vertical scaling can be expensive\n- Performance challenges at huge scale\n- Schema changes can be disruptive\n- Harder to manage large volumes of unstructured data" as SQL
+
+' NoSQL Databases
+rectangle "NoSQL Databases\n\n+ Flexible schema (schema-less)\n+ Horizontal scaling (sharding, clusters)\n+ High performance for large data volumes\n+ Easier to store unstructured/semi-structured data\n+ Typically faster read/write operations\n+ Strong integration with modern development practices\n\n\n- Eventual consistency (BASE model)\n- Limited support for complex queries/transactions\n- Varied querying methods (no standard query language)\n- Less mature ecosystem\n- Can lead to data duplication\n- May require more application-side logic" as NoSQL
+
+' Layout
+left to right direction
+
+Legend -[hidden]-> SQL
+SQL -[hidden]-> NoSQL
+
+@enduml

cloud_analysis/database host comparison/all_comparison.puml

@@ -0,0 +1,44 @@
+@startuml
+skinparam padding 20
+skinparam backgroundColor #000000
+skinparam shadowing false
+skinparam rectangle {
+  BackgroundColor Black
+  BorderColor White
+  FontColor White
+  RoundCorner 25
+  FontSize 13
+  MinWidth 220
+  MinHeight 200
+}
+
+title "<color:white><size:20><b>Cloud Database Host Comparison</b></size></color>"
+
+' Legend
+rectangle "Legend\n\n+ = Advantage (Pro)\n- = Limitation (Con)" as Legend
+
+' MongoDB Atlas
+rectangle "MongoDB Atlas\n\n+ Scales well\n+ Flexible schema\n+ Global clusters\n\n+ Strong documentation\n- Complex query tuning\n- Index management needed\n- Learning curve for new users" as Mongo
+
+' AWS RDS
+rectangle "AWS RDS\n\n+ Stable, high availability\n+ Fully managed SQL\n+ Supports PostgreSQL, MySQL, etc.\n+ Excellent for legacy systems\n\n- More complex to configure\n- Higher cost\n- Vendor lock-in" as RDS
+
+' Firebase
+rectangle "Firebase\n\n+ Realtime data sync across clients\n+ Integrated with Google Cloud\n+ Great for mobile and web apps\n+ Built-in auth and analytics\n+ Offline support\n\n- Limited querying\n- No SQL support (uses NoSQL)\n- Complex pricing\n- Vendor lock-in\n- Less control over schema" as Firebase
+
+' Supabase
+rectangle "Supabase\n\n+ Open-source Firebase alternative\n+ Full SQL (PostgreSQL)\n+ Real-time subscriptions\n+ Built-in auth & storage\n+ Self-host or managed\n\n- Smaller community\n- Can be slower at scale\n- Limited cloud regions\n- Fewer enterprise tools\n- Some hosted bugs" as Supabase
+
+' PostgreSQL
+rectangle "PostgreSQL\n\n+ Advanced SQL capabilities\n+ Strong data integrity\n+ JSON support\n+ Highly extensible\n+ Open-source\n\n- Manual tuning often required\n- Heavier setup for scaling\n- Slower queries at high volume" as Postgres
+
+' Layout
+left to right direction
+
+Legend -[hidden]-> Mongo
+Mongo -[hidden]-> RDS
+RDS -[hidden]-> Firebase
+Firebase -[hidden]-> Supabase
+Supabase -[hidden]-> Postgres
+
+@enduml