Resource Event Source for Notification Based External Events

Abierto

#1,514 abierto el 4/10/2022 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad: 5/5
Tiempo estimado: Más de una semana
Aptitud para principiantes: 35/100

Tipo de issue: Nueva funcionalidad
Claridad: Bastante claro
Estado de actividad: Estancado
Stack tecnológico: java
Área: backend

Línea de trabajo

Comienza leyendo las implementaciones existentes de CachingInboundEventSource, PollingEventSource y PerResourcePollingEventSource para comprender su comportamiento de eventos y de caché. El trabajo estará completo cuando una notificación entrante sin un recurso obtenga y almacene en caché todo el recurso externo y, a continuación, propague un evento de cambio al manejador de eventos.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

eventsources-epic feature on-demand

For Kubernetes resources we already have this cache in Informer, for external resources we have the CachingInboundEventSource for a resource oriented event coming from an external system. And two flavors of polling event source: PollingEventSource and PerResourcePollingEventSource.

What we don't have covered is the situation for an external resource when it is capable to notify about change, but the notification not contains the resource it self. Typically such external events are comming from AWS resources, like from RDS:
see: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-cloudwatch-events.sample.html
A sample event does not contains the resource itself.
( see also: Event Notification https://martinfowler.com/articles/201701-event-driven.html )

We have two options here either the dependent resource fetches the resource on reconcile and puts it into local cache. Or we prepare an even source that when receives an inbound event also fetches and caches the resource (then triggers and event).
This would be much more optimal, since we just don't fetch resource on every reconcile. So the event source logic should look like this:

sequenceDiagram
    participant InboundFetchingEventSource
    participant ExternalService
    participant EventHandler
    ExternalService->>InboundFetchingEventSource: Send Resource Changed Event
    InboundFetchingEventSource->>ExternalService: Fetch The Whole Resource
    InboundFetchingEventSource->>InboundFetchingEventSource: Cache The Resource
    InboundFetchingEventSource->>EventHandler: Propagate Event About The Change

Lenguaje dominante: Java
Estrellas: 944
Forks: 242
Merge medio: 1 d 4 h
PR fusionados (30 d): 43