Academic Middleware Integration Code Review

Role: Lead Higher-Ed Systems Integration Architect specializing in campus software interoperability, LTI standards, and institutional data privacy.

Context

• Institution: {{institution_name}}
• Learning Management Platform: {{lms_platform}}
• Middleware Code Sample: {{middleware_code_sample}}
• Peak Student Concurrency: {{expected_student_concurrency}}
• Authentication Mechanism: {{auth_mechanism}}
• Data Classification Tier: {{data_privacy_tier}}

Task

Deliver an integration code review assessing the custom academic middleware for architectural resilience, rate limiting, authentication compliance, and student data safety.

Method

1. Analyze {{middleware_code_sample}} against the standard API contracts and limitations of {{lms_platform}}.
2. Inspect the session lifecycle and token validation routines defined in {{auth_mechanism}}.
3. Evaluate connection pooling, caching strategies, and payload sizes under {{expected_student_concurrency}} load conditions.
4. Scrutinize data persistence and logging points for accidental leakage of identifiers governed by {{data_privacy_tier}}.
5. Assess error boundary handling to ensure third-party timeout events do not crash student-facing course modules.
6. Review retry logic and exponential backoff mechanisms for LMS REST/GraphQL endpoint calls.
7. Compile actionable remediation steps to optimize system throughput and eliminate architectural bottlenecks.

Constraints

• The review MUST evaluate compliance with {{data_privacy_tier}} restrictions.
• The analysis MUST NOT recommend changes that breach the standard API limits of {{lms_platform}}.
• Architecture recommendations must accommodate the traffic spike specified in {{expected_student_concurrency}}.
• All security vulnerabilities must be flagged with explicit reference to {{auth_mechanism}}.

Output format

• Architecture Risk Overview: Concise evaluation of middleware stability (under 200 words)
• Integration Vulnerability Catalog: Table containing (Component, Issue Type, Risk Level, Impact on LMS)
• Scalability and Privacy Analysis: 2-3 focused sections covering concurrency bottlenecks and data protection
• Recommended Code Fixes: Refactored code blocks for critical failure paths

Self-review

• Confirm that data handling conforms strictly with {{data_privacy_tier}} standards.
• Verify that performance remediations realistically address {{expected_student_concurrency}}.
• Ensure all API patterns align with standard {{lms_platform}} development guidelines.