咨询股票期权投资组合动态监控应用的技术需求

Nice work getting your MVP off the ground with TDD in .NET Core—building an options portfolio tracker is a great project, especially with the ETrade integration constraints. Let’s walk through the key technical requirements you’ll want to lock in as you expand beyond your initial logic:

ETrade API Integration & Authentication #

• OAuth 1.0a Compliance: ETrade uses OAuth 1.0a (not OAuth2) for authentication, so you’ll need to implement the full flow: request token, user authorization, access token exchange, and token refresh. Store credentials securely—use .NET User Secrets for development, and production-grade secrets management like Azure Key Vault or environment variables (never hardcode keys/tokens).
• Position & Market Data Retrieval: Call ETrade’s Get Option Positions endpoint to pull your holdings, but don’t stop there—you’ll need real-time underlying stock prices (via ETrade’s market data API) to calculate accurate option values. Parse response data carefully, especially option Greeks (delta, gamma, theta) which are critical for tracking portfolio risk.
• Rate Limiting & Error Handling: ETrade enforces API rate limits, so implement retry logic with backoff (the Polly library is perfect for this in .NET). Handle common errors like 401 (expired tokens) by triggering an automatic refresh, and 5xx server errors with retries.

Scheduling & Timezone Precision #

• Timezone-Aware Execution: Since your app needs to run 9:30 AM–4:00 PM ET (Mon-Fri), never rely on local system time. Use .NET’s TimeZoneInfo to explicitly target the Eastern Time Zone with TimeZoneInfo.FindSystemTimeZoneById("Eastern Standard Time")—this automatically accounts for daylight saving time changes.
• Robust Task Scheduling: Use a mature .NET scheduling library like Quartz.NET or Hangfire to define recurring jobs. For Quartz, configure a DailyTimeIntervalTrigger that runs only on weekdays, between your target hours. Ensure jobs don’t overlap (use a mutual exclusion lock or job persistence) to avoid hitting ETrade’s rate limits with concurrent requests.

Data Persistence & State Management #

• Historical Data Storage: Track portfolio changes over time by storing position data, option values, and market prices in a database. For a lightweight setup, use SQLite with Entity Framework Core (EF Core) — it’s easy to integrate, works well with TDD (use in-memory databases for unit tests), and doesn’t require a full server. For scaling later, switch to SQL Server or PostgreSQL.
• In-Memory Caching: Use .NET’s IMemoryCache to store current portfolio state and recent market data to reduce API calls. Set short cache expiration times (e.g., 1–5 minutes) to balance performance and data freshness.

Business Logic Enhancements #

• Option Valuation: While ETrade may return some Greeks, you might need custom calculations (e.g., Black-Scholes model) for real-time what-if scenarios. Use libraries like MathNet.Numerics to implement these formulas without reinventing the wheel.
• Alerting & Notifications: Add rule-based alerts (e.g., "notify me if my portfolio’s delta exceeds 0.5" or "alert on 10% loss in an option position"). Integrate with services for email/SMS notifications to keep you updated on critical changes.
• Structured Logging: Implement logging with Serilog or NLog to track API calls, job executions, and errors. Log at different levels (Info, Warn, Error) and persist logs to files or a centralized system for easy debugging.

Security Best Practices #

• Credential Protection: As mentioned earlier, avoid hardcoding secrets. Use .NET’s Data Protection API to encrypt sensitive data stored locally, or encrypt database fields containing account-specific information.
• Least Privilege: Configure your ETrade API app with only the permissions it needs (e.g., read-only access to positions and market data) to minimize risk if credentials are compromised.

Testing Extensions for TDD #

• Mocked API Integration Tests: Don’t hit the real ETrade API in automated tests—use Moq to mock your API client, or WireMock to spin up a local mock server that replicates ETrade’s response formats. This keeps tests fast and avoids rate limit issues.
• Time Mocking: For scheduling tests, abstract time into an ISystemClock interface so you can inject mock time values and verify jobs run at the correct intervals without waiting for real-world time to pass.

内容的提问来源于stack exchange，提问作者Robert Green MBA