[teiid-issues] [JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates

[Ramesh Reddy (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560762#comment-13560762 ] 

Ramesh Reddy commented on TEIID-5285:
-------------------------------------

Since the user is not really after any virtualization aspects, IMO this needs to be transparent. Sure the assumption is the usage of Teiid SQL is mandated. In order to be transparent, we need to generate either Entities or VDB or both with Spring Boot. I feel, Annotation based approach will not work best here as it involves work from the developer and needs to have Teiid knowledge, we need to remove that obstacle. Generating VDB will remove that. Now after generation of the VDB, we can still make Spring Boot as the execution environment if needs to be embedded with the application, or if we take sidecar approach then we can use spring-boot or swarm. Either case the user would need to generate the Entities for their domain model.

I think we should consider Annotation based code generation, only if we are going to give the developers a starting point to modify the View-based entities.

I was thinking about sidecar approach to enable this for supporting more languages, but we can progress from one approach to another. Yes, when sidecar deploys it is in the same Pod as a different container which is the same host.


> Add high-level feature for redirection of updates
> -------------------------------------------------
>
>                 Key: TEIID-5285
>                 URL: https://issues.jboss.org/browse/TEIID-5285
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Query Engine, Teiid Spring Boot
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 10.3
>
>
> In microservices testing it is desirable to test against production/live data but not commit any updates.  We should offer a simple solution that can defined by extension metadata and enabled/disabled by a feature flag.  We may need to make simplifying assumptions about the scope (per session, per application, etc.) and durability of the updates.
> Under the covers this will be achieved by using views, update triggers, and a store for the updates and when not enabled the expectation is that all operations should pass through.  However the application will be limited to using Teiid SQL and will be required to use the Teiid or pg driver, or Teiid spring boot.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)