Skip to content

Commit e14db25

Browse files
author
pellse
committed
Update README.md to reflect api change from autoCache to 'streamTable'
1 parent fda8d43 commit e14db25

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -445,10 +445,10 @@ var assembler = assemblerOf(Transaction.class)
445445
```
446446
[:arrow_up:](#table-of-contents)
447447

448-
### Auto Caching
448+
### Stream Table
449449
In addition to the cache mechanism provided by the `cached()` and `cachedMany()` functions, ***Assembler*** also provides a mechanism to automatically and asynchronously update the cache in real-time as new data becomes available via the `streamTable()` function. This ensures that the cache is always up-to-date and avoids in most cases the need for `cached()` to fall back to fetch missing data.
450450

451-
The auto caching mechanism in ***Assembler*** (via `streamTable()`) can be seen as being conceptually similar to a `KTable` in Kafka. Both mechanisms provide a way to keep a key-value store updated in real-time with the latest value per key from its associated data stream. However, ***Assembler*** is not limited to just Kafka data sources and can work with any data source that can be consumed in a reactive stream.
451+
The Stream Table mechanism in ***Assembler*** (via `streamTable()`) can be seen as being conceptually similar to a `KTable` in Kafka. Both mechanisms provide a way to keep a key-value store updated in real-time with the latest value per key from its associated data stream. However, ***Assembler*** is not limited to just Kafka data sources and can work with any data source that can be consumed in a reactive stream.
452452

453453
This is how `streamTable()` connects to a data stream and automatically and asynchronously update the cache in real-time:
454454

@@ -483,7 +483,7 @@ var transactionFlux = getCustomers()
483483
.flatMapSequential(assembler::assemble);
484484
```
485485

486-
It is also possible to customize the Auto Caching configuration via `streamTableBuilder()`:
486+
It is also possible to customize the Stream Table configuration via `streamTableBuilder()`:
487487

488488
```java
489489
import reactor.core.publisher.Flux;
@@ -501,7 +501,7 @@ import static io.github.pellse.assembler.caching.StreamTableFactory.OnErrorMap.o
501501
import static reactor.core.scheduler.Schedulers.newParallel;
502502
import static java.lang.System.getLogger;
503503

504-
var logger = getLogger("auto-cache-logger");
504+
var logger = getLogger("stream-table-logger");
505505

506506
Flux<BillingInfo> billingInfoFlux = ... // From e.g. Debezium/Kafka, RabbitMQ, etc.;
507507
Flux<OrderItem> orderItemFlux = ... // From e.g. Debezium/Kafka, RabbitMQ, etc.;
@@ -532,7 +532,7 @@ By default, the cache is updated for every element from the incoming stream of d
532532

533533
[:arrow_up:](#table-of-contents)
534534

535-
### Event Based Auto Caching
535+
### Event Based Stream Table
536536
Assuming the following custom domain events not known by ***Assembler***:
537537
```java
538538
sealed interface MyEvent<T> {

0 commit comments

Comments
 (0)