Possibility of using Ebean Elasticsearch for the massive transaction list of OLTP applications

37 views
Skip to first unread message

Mike Zhao

unread,
Jul 17, 2023, 7:42:08 PM7/17/23
to Ebean ORM
Hi, Group,

It is a frequently used design to use Elasticsearch in eCommerce to enhance the searching experience on the website, e.g., the list of products, or webpages. Examples include Magento catalog search and Odoo Smart Search.

In the above examples, Elasticsearch works as a search engine, dealing with thousands of records in the typical case. For example, an online store of a medium-or-small-sided business usually lists one thousand products at most.

The online document of Ebean Elasticsearch mentioned an example of product prices getting refreshed every midnight, so the use case is like the catalog searching above.

The video presentation mentioned another example of Ebean working on the customer information database. So, it is supposed to be a bigger data size than the catalog, because multiple customers are purchasing the same product.

Looking further, we are considering working on the massive transaction list of an OLTP (on-line transaction processing) system, in the hope of improving searching on the text columns.

For example, the credit card gateway often processes millions of transactions per day, and a report or customer inquiry often needs to include months of raw data.

Our Question:

Is it feasible to use Elasticsearch?

And if yes, do we have an example, e.g., an open source project? Or, if no, do we have a reason to firmly rule out this direction?

We are new to this area, and we highly appreciate hints and suggestions.


Rob Bygrave

unread,
Jul 19, 2023, 1:07:46 AM7/19/23
to eb...@googlegroups.com
> Is it feasible to use Elasticsearch?

This question needs to go to ElasticSearch and not Ebean really.

Ultimately you might look to do your own "Proof of Concept" at close to the expected scale in terms of amount of data etc.


> highly appreciate hints

In my opinion this area is very much non-trivial with a lot of options to consider around data types and partitioning etc and a lot depends on the types of queries that are expected to be needed.


Note that ebean-elastic is an elasticsearch client but it's future is in doubt. There is consideration that it might be removed from ebean going forward in a later version of ebean in order to simplify ebean itself.  Refer to https://github.com/ebean-orm/ebean/discussions/3112


Cheers, Rob. 



--

---
You received this message because you are subscribed to the Google Groups "Ebean ORM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ebean+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ebean/380a82df-3140-4cec-a346-50cf4b38e70dn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages