Apex Beginner to Advance
- Apex Fundamentals
- Core Apex Programming
- Object-Oriented Programming
- Triggers & Automation
- Asynchronous Apex
- Integrations & APIs
- Testing & Deployment
- Security & Performance
- Real-World Apex Projects
- Project 1 – Validation Trigger in Apex
- Project 2 – Simple REST API in Apex
- Project 3 – Auto-Number Generator in Apex
- Project 4 – Scheduled Cleanup Job in Apex
- Project 5 – Trigger Framework Implementation
- Project 6 – Batch Data Migration Tool in Apex
- Project 7 – Secure External Integration in Apex
- Project 8 – Dynamic PDF Generator using Apex (Spring ’26)
- Project 9 – Queueable Job Orchestration
- Advanced Apex & Platform Architecture
- Apex Design Patterns: Why They Matter
- Singleton & Factory Patterns in Apex
- Strategy Pattern for Business Rules in Apex
- Service Layer & Domain Layer Architecture
- Selector Layer & Query Centralization
- Dependency Injection in Apex
- Apex Enterprise Patterns (fflib Overview)
- Unit of Work Pattern & Transaction Control
- Feature Flags Using Custom Metadata
- Refactoring Apex Without Breaking Production
Named Credentials in Salesforce
Hardcoding API URLs, usernames, passwords, or tokens inside Apex code is dangerous and unscalable. Salesforce provides Named Credentials to securely manage - Endpoints, Authentication, Token rotation, User access, Environment changes.
