Use Cases

[benjchristensen]

Documenting use cases.

[benjchristensen]

Event processing with enrichment:

• Persistent connection over TCP
• milliions of events/second
• for each event asynchronously fetch data via network to enrich event
• conditional logic per enriched events
• write event to event bus
• separate consumers in JVM process subscribed to the event bus

[benjchristensen]

Proxy:

• request/response using HTTP/1.1, persistent Websockets or HTTP/2 connections with message passing
• intercept request
  • decorate or enrich
  • authorization and authentication
  • logging
  • metrics
• conditional routing to backend services over network depending on request
• route response back
• intercept response
  • decorate or enrich
  • logging
  • metrics
  • compression

[benjchristensen]

Webservice:

• HTTP/1.1, HTTP/2, Websockets, SSE
• request/response
• request/stream
• message passing
• intercept
  • metrics
  • logging
  • tracing
  • debugging
  • fault injection
  • caching
  • load shedding

[benjchristensen]

Interception:

• return response from cache instead of normal handler
• security
• load shedding
• tracing, debugging, inspection
• logging, auditing
• fault injection
• compression
• SSL termination
• stubbing/mocking

[benjchristensen]

Server/Client-as-a-Function:

• declare a server or client
• compose new functionality/behavior via interception onto a server or client
• allow reusable components via composition, interception and layering without tight coupling

[benjchristensen]

Connection pooling:

• ability to inject behavior for pooling of connections
• pooling implementation should be able to implement whatever load balancing algorithms it wishes
• feedback loops for metrics and health must be provided to the pool
• control of connection establishment and tear down must be available to the pool