是否需结合Hyperledger Composer REST API与Fabric SDK API实现更多功能？

Absolutely—combining these two sets of APIs is not just acceptable, but often the best approach when you need both business-focused operations and access to Hyperledger Fabric's underlying capabilities. Let me break down why and how to go about it:

When to Use Each API #

Hyperledger Composer REST API #

The Composer REST API is built specifically around your Business Network Definition (BND). It’s perfect for:

• Rapidly exposing CRUD operations for your assets, participants, and transactions
• Executing business logic defined in your Composer transactions
• Handling role-based access control tied to your business network
• Avoiding the complexity of writing low-level Fabric code for standard business workflows

If your use case aligns with these, stick with the Composer REST API—it’s designed to save you time and keep your code focused on business logic.

Direct Hyperledger Fabric APIs #

When you need to go beyond what the Composer REST API offers (like deep world state queries or Fabric-specific infrastructure tasks), direct Fabric APIs (via SDKs like Node.js or Java) are your go-to. Common scenarios include:

• Advanced world state queries:
  • Fetching the full history of an asset (using getHistoryForKey)
  • Running raw chaincode queries that aren’t mapped to your Composer business model
  • Querying all key-value pairs in the world state (not just those defined in your BND)
• Fabric infrastructure operations:
  • Managing channels (creating, updating, joining)
  • Inspecting block data (block height, transaction details within blocks)
  • Monitoring peer/orderer node health
  • Managing identity certificates and MSP configurations

How to Combine Them Effectively #

• Split responsibilities: Use the Composer REST API for all core business workflows (e.g., creating a product asset, initiating a transfer transaction) and reserve Fabric APIs for edge cases that require low-level access.
• Maintain consistent identity context: Ensure the identity used for both APIs has the necessary permissions. Composer identities are tied to your business network, while Fabric identities are MSP-based—make sure they’re aligned to avoid permission errors.
• Avoid redundancy: Don’t rewrite functionality that the Composer REST API already handles well. For example, there’s no need to call Fabric’s invokeChaincode to create an asset when you can use the Composer REST API’s POST endpoint for that asset type.

Key Considerations #

• Version compatibility: Double-check that your Composer version is compatible with your Fabric version (e.g., Composer v0.20.x works with Fabric v1.4.x). Mismatched versions can cause unexpected behavior.
• Complexity tradeoff: Direct Fabric APIs require handling more low-level details (like endorsement policies, serialization, and peer communication). Only use them when the value of the functionality outweighs the added complexity.

内容的提问来源于stack exchange，提问作者sun