stwissel / vertx-sfdc-platformevents

Salesforce Platform Events Client for vert.x integration

Salesforce vert.x integration

Collection of verticles that enable interaction with the Salesforce API Check the full documentation!

Current released version

The current released version is 0.3.3
Development might have newer snapshots

Available Verticles

• Authentication
• Subscription to platform events
• Process platform events
• Main/Setup Verticle
• Deduplication Verticle (messages already processed get discarded

Check the full documentation!

Setup and Configuration

Add this dependencies to your pom.xml:

<dependency>
	<groupId>net.wissel.salesforce</groupId>
	<artifactId>vertx-sfdc-core</artifactId>
	<version>0.3.3</version>
</dependency>
<!-- Optional for deduplication service if Redis is your choice -->
<dependency>
	<groupId>net.wissel.salesforce</groupId>
	<artifactId>vertx-sfdc-redis</artifactId>
	<version>0.3.3</version>
</dependency>

Check the full documentation!

Artifacts on Maven Central

Change Log

List of changes in reverse order

Issues and feedback

I would love to hear about your implementation or ideas or challenges, so open an issue on GitHub - even for sharing success. Don't be shy!

vertx-sfdc-platformevents's Issues

Create Consumer to log Verticle

Create RX Version of Verticles

Create startup sequence

Consumer to Redis Verticle

Create authentication Verticle

Improve documentation

The official site can use more examples and explanations

Broken link to SF Sample Artefacts page

Hey Stephan,

There's a link to https://github.com/stwissel/sfdc-vertx-sample from your main doco page.

This link is broken. You probably know that :-)

O.

Consumer to Redis Verticle

Create interactive subscription web module

Design shutdown sequence

Add circuit breaker logic to consumers

Create user authentication

Use SFDC OAuth module

Consumer to MQTT Verticle

Create Consumer to SOAP callback

Consumer to SMS Verticle

Create Main Verticle

Loader verticle that reads configuration and prepares all other verticles

Allow arrayed subscriptions

SFDC platform events allow arrayed subscriptions, so one listener can receive multiple events counting only one against platform event subscriber limits

Create unit tests

Create web server API

Create OBM listener

Besides Platform events we could listen to Outbound messages as well.

Consumer to Kafka Verticle

Create CometD listener verticle

Setup Codeship to publish to Nexus

• Build automation
• GPG signing
• Test

Remove System.out.println statements

That stuff belongs in the log, not the console

Create configuration object

Extract CometD logic into handler class

Currently CometD logic is hard-wired into a verticle which makes testing it harder than it needs to be. Extract into a helper class that can be unit tested without a running http server.

Consumer to SMTP Verticle

Create mock server

When testing the Verticles some mock server needs to answer all the requests. Can be configured in testingconfig.json

Document wire protocol

How the verticles talk to each other

Documentation configuration options

Restructure project to split artifacts

Users should be able to only load what they need. Splitting into:

• Parent Project (POM)
• Core
• Redis
• etc.

Create Consumer to webSocket Verticles

Create Consumer to Rest service call back

On shutdown allow individual verticles of the same class

Currently all verticles instances of one class listen to the same shutdown address. This prevents individual listeners to be shut down. Should be based on verticle name

Consumer to MQ Verticle

Make subscription behaviour configurable

Currently the API replays all events of the EventQueue on subscription.
A configuration option should allow to specify all|none|tip

Deduplication of messages required

When a queue restarts or multiple concurrent listeners receive the same message, we need to ensure that we don't have any duplicate messages provided to the consumer.

Have an implementation that does that in memory and can be overwritten in another module with a central key value store

Prepare 0.1 release

• Update documentation
• Switch System.out to logger.info