Introducing Opensearch in existing multisource enterprise App
summary
Case study of adding OpenSearch to an app that keeps data in Oracle DB and MongoDB without migrating: change data capture uses Debezium + Kafka CDC to stream updates, a custom Spring Boot Kafka consumer resolves joins across multiple tables into single searchable documents, writes to OpenSearch, and enforces end‑to‑search latency monitoring with a 500 ms threshold. Uses Kafka’s delivery guarantees for effectively once processing; scaled in production and delivers a single unified search UI across both sources.
AI-written summary · about
related talks
40mOperating Opensearch - The Kubernetes Way
09mUnconference: OpenSearch is not a database!
39mFlexible OpenSearch Data Management With Apache Iceberg: Data...
24mReimagining Search : Scaling OpenSearch Across an Enterprise - Platform C...
35mInnovating at Scale: Lessons from Pegasystems' OpenSearch Journey
35mPlatformizing OpenSearch at Uber
05mKeynote: OpenSearch: From Code to Community
41mDynamoDB, Neptune and OpenSearch: A Unified Approach to Collaborative Editing and Search #JSConfAM25