Skip to content

Commit

Permalink
add MySQL engine
Browse files Browse the repository at this point in the history
  • Loading branch information
BlackbitDevs committed Aug 15, 2024
1 parent 6116502 commit a65f4d1
Showing 1 changed file with 458 additions and 0 deletions.
Loading

2 comments on commit a65f4d1

@somegooser
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks promising. What are the advantages over Sqlite?

@nticaric
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The main advantage of storing the index in MySQL instead of SQLite is that it removes the dependency on a filesystem. For scenarios like serverless environments or containerized applications where persistent local storage isn’t guaranteed or even available (e.g., AWS Lambda, or when using cloud storage like S3), SQLite’s file-based approach becomes a challenge. In these cases, SQLite simply isn't a viable option.

On the other hand, storing the index in MySQL means that everything remains within a database accessible over the network. By using MySQL as the index store, your application remains more flexible and scalable without being constrained by the limitations of filesystem storage.

Overall, it’s about providing more options for where and how the search engine can be deployed, making it easier to integrate TNTSearch in cloud-native and distributed setups.

Please sign in to comment.