3.7 Steps to Adopt Multi in Existing Service
This topic provides the systematic instruction to adop multi in existing service.
Plato Micro Service Dependencies Changes
compile("release.obma.plato.21_0_0.services:plato-microservice-dependencies:6.0.0")Eventhub dependency changes
compile("release.obma.plato.21_0_0.services:plato-eventhub-dependencies:6.0.0")PlatoInterceptor Changes
@Bean public MappedInterceptor gemInterceptor(PlatoInterceptor
platoInterceptor) {
LOG.info("Added interceptor for fetching the application headers"); return new
MappedInterceptor(new String[] { "/**" }, platoInterceptor);
}
Logging (Please include only ,%X{entityId}, change. Rest of them remain as per the old logback.xml)
Please include only %X{entityId} in the existing value of the LOG_PATTERN of your logba
c k.xml
One sample format is below,
<property name="LOG_PATTERN" value="%clr(%d{yyyy-MM- dd
HH:mm:ss.SSS}){faint} %clr(%5p [${applicationName},%X{entityId},%X{X-B3-
TraceId:},%X{X-B3-SpanId:-},%X{X-Span-Export:-}]) %clr([%mdc{env:-null}] [%mdc{tenant:- null}]
[%mdc{user:-null}] [%mdc{branch:-null}]){faint} %clr(${PID:- }){magenta} %clr(--
-){faint} %clr([%15.15t]){faint} %clr(%-
40.40logger{39}){cyan} %clr(:){faint} %m%n${LOG_EXCEPTION_CONVERSION_WORD:-%wEx}" />Feed Services
Folder structure should be */parentFolder/<<entityId>>/{fileName}
compile("release.obma.plato.21_0_0.services:plato-feed-core:6.0.0")Caching Strategy
@Cacheable(value = "customers", key = "{ <<funtionalKeys>> T(oracle.fsgbu.plato.core.per
sistence.provider.PlatoHolder).getCurrentEntityId() }")Introduce appId in application.yml of individual micro services
If the service is a eventhub based service they should use
spring:
application:
appID:
If the service is a non-eventhub based service they can use either
spring:
application:
appID:
or
appId: <<appId>>Parent topic: Service Extensions