azure-eventhub-java
Azure Event Hubs Java SDK
Build real-time streaming applications with Azure Event Hubs SDK for Java. Use for event streaming, high-throughput data ingestion, and event-driven architectures.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「azure-eventhub-java」を使用しています。 Create an EventHubProducerClient with DefaultAzureCredential
期待される結果:
EventHubProducerClient producer = new EventHubClientBuilder()
.fullyQualifiedNamespace("<namespace>.servicebus.windows.net")
.eventHubName("<event-hub-name>")
.credential(new DefaultAzureCredentialBuilder().build())
.buildProducerClient();
「azure-eventhub-java」を使用しています。 Send events in batch with partition key
期待される結果:
CreateBatchOptions options = new CreateBatchOptions()
.setPartitionKey("customer-123");
EventDataBatch batch = producer.createBatch(options);
batch.tryAdd(new EventData("Customer event"));
producer.send(batch);
セキュリティ監査
安全All static findings are false positives. The skill is documentation for Azure Event Hubs Java SDK. The external_commands alerts (38 occurrences) are triggered by backticks in markdown code blocks - these are code examples, not shell commands. The weak_crypto and system_reconnaissance alerts are misinterpretations of documentation text (partition keys, checkpointing). No actual security risks present.
品質スコア
作れるもの
Build event streaming pipelines
Create event producers and consumers for real-time data streaming between systems
Implement high-throughput data ingestion
Handle millions of events per second with batch processing and partition strategies
Create scalable microservices communication
Use Event Hubs as message backbone for microservices event-driven communication
これらのプロンプトを試す
Show me how to create an EventHubProducerClient using a connection string in Java
How do I create an EventHubConsumerClient to receive events from a specific partition?
Implement an EventProcessorClient with BlobCheckpointStore for production-scale processing
Show me how to use EventHubProducerAsyncClient for non-blocking event sending
ベストプラクティス
- Use EventProcessorClient for production workloads to get automatic load balancing and checkpointing
- Batch events using EventDataBatch for efficient network utilization
- Always close clients using try-with-resources to ensure proper cleanup
回避
- Do not hardcode connection strings in source code - use environment variables or Azure Key Vault
- Avoid sending events one at a time - use batching for throughput
- Do not skip checkpointing - this leads to reprocessing events on restart