diff --git a/work/synadia_prep.md b/work/synadia_prep.md
index 3134f1b..cdddd79 100644
--- a/work/synadia_prep.md
+++ b/work/synadia_prep.md
@@ -1,3 +1,99 @@
+# NATS Technical Reference Guide for IoT and Smart Cities
+
+## 1. Introduction to NATS
+
+NATS (Neural Autonomic Transport System) is a high-performance messaging system written in Go, designed for building distributed systems and microservices. It offers a modern approach to communication, overcoming limitations of traditional messaging systems.
+
+### Key Features:
+- Lightweight and high-performance
+- Easy to use with simple APIs
+- Highly scalable
+- Fault-tolerant with built-in redundancy
+- Secure by design
+
+## 2. NATS vs Traditional Communication Systems
+
+| Aspect | Traditional Systems | NATS |
+|--------|---------------------|------|
+| Discovery | Cumbersome via HTTP/DNS | Dynamic and efficient service discovery |
+| Communication | Limited 1:1 | Flexible M:N patterns |
+| Data Transfer | Pull-based semantics | Push, pull, and fan-in/fan-out support |
+| Security | Perimeter-based | Zero trust model |
+| Routing | Via gateways, proxies, load balancers | Intelligent routing without additional infrastructure |
+| Backend | Centralized, location-dependent | Decentralized, bringing data closer to users |
+
+## 3. NATS Architecture and Components
+
+### 3.1 Core Concepts
+- **Subjects**: Named channels for publishing messages
+- **Publishers**: Clients that send messages to subjects
+- **Subscribers**: Clients that receive messages from subjects
+- **NATS Server**: The message broker that routes messages
+
+### 3.2 Communication Patterns
+- **Publish-Subscribe (Pub/Sub)**: One-to-many message distribution
+- **Request-Reply**: Synchronous communication for query-response scenarios
+- **Queue Groups**: Load balancing for horizontally scaled services
+
+## 4. NATS in IoT and Smart Cities
+
+### 4.1 Use Case: Smart Traffic Management
+- **Components**: Smart traffic lights, connected vehicles, environmental sensors, CCTV cameras
+- **Data Flow**: 
+  1. Devices publish data to NATS subjects
+  2. Central system subscribes to relevant subjects
+  3. AI/ML algorithms process data for traffic optimization
+  4. Control messages sent back to devices via NATS
+
+### 4.2 Benefits in IoT Scenarios
+- Scalability to handle millions of connected devices
+- Low-latency communication for real-time data processing
+- Flexible communication patterns suitable for various IoT applications
+- Efficient data aggregation using fan-in patterns
+
+## 5. Security Features
+
+- **Authentication**: Support for username/password, NKEYS, and JWT
+- **Authorization**: Fine-grained control over publish/subscribe permissions
+- **Encryption**: TLS for secure communication
+- **Account Isolation**: Multi-tenancy support for isolating different applications or customers
+
+## 6. Performance Considerations
+
+- **Throughput**: Capable of millions of messages per second
+- **Latency**: Sub-millisecond latency in optimal conditions
+- **Scalability**: Horizontal scaling by adding more NATS servers to the cluster
+
+## 7. Best Practices for NATS Implementation
+
+1. Use meaningful subject names for easy management
+2. Implement proper error handling and reconnection logic
+3. Leverage NATS streaming for scenarios requiring message persistence
+4. Use queue groups for load balancing in microservices architectures
+5. Regularly monitor NATS server metrics for performance optimization
+
+## 8. Comparison with Other Messaging Systems
+
+| Feature | NATS | Kafka | RabbitMQ |
+|---------|------|-------|----------|
+| Latency | Very Low | Low | Low |
+| Throughput | Very High | Very High | High |
+| Persistence | Optional (with JetStream) | Built-in | Optional |
+| Complexity | Low | High | Medium |
+| Use Case | Real-time, Microservices | Big Data, Stream Processing | General Purpose |
+
+## 9. Conclusion
+
+NATS provides a robust, scalable, and flexible messaging solution ideal for IoT and smart city applications. Its ability to handle high-throughput, low-latency communication makes it well-suited for real-time data processing and control systems in urban environments.
+
+## 10. Further Resources
+
+- [NATS.io Official Documentation](https://docs.nats.io/)
+- [NATS GitHub Repository](https://github.com/nats-io/nats-server)
+- [NATS by Example](https://natsbyexample.com/)
+
+---
+
 ### Detailed Technical Study Guide for Synadia Technical Solutions Architect (TSA) Role
 
 #### Overview