Came up with an idea to build an API-based Partner Payout Product where we can configure actual and scenario-based contracts and execute them in real time. Besides the actual partner bill report, the user can also perform any payout-related query via scenario-based contracts (with or without a rate card). Users can define their user types (free, paid, free > 100) based on multiple filters, stream count range, etc. And later marge themwith the help of an alias name. Enable multiple rate card calculations based on the slab, user streams, and subscription type. Onboarding a new partner is relatively easier.

OneCustomer View is built for data consolidation frommultiple business units. Synchronizes data from multiple data sources i.e. MySQL, Cassandra, MongoDB, SFTP, Kafka, and third-party APIs. Automate the process for adding new databases or tables into Hive. Generate hourly lag status reports for every database and table (over more than 500 tables). Use ElasticSearch to build a search engine for internal queries. Create ElasticSearch Schema with custom analyzers for different searching features.

Parse the RDF input data with Apache Jena. Load the open-source database within a GraphDatabase and query the same. Pre-process the graph and store the result in a defined index schema for spotting entities, categories, and disambiguating them based on semantic links. Extract noun phrases from input data. For each noun phrase, search the n-grams in elasticsearch. Spotting the entities, categories, and disambiguating them.