Skip to content

Microsoft.SemanticKernel.Memory vs Kernel-Memory #736

Answered by dluc
hemantkathuria asked this question in 1. Q&A
Discussion options

You must be logged in to vote

Hi @hemantkathuria - high level, there's a fundamental difference that KM is a service, you can deploy and use it, while SK allows to build apps and services.
That said, there are several things we learned and keep learning while we keep working on KM, and the plan is to port some features from KM to SK Memory. For instance, the ability to filter records not just by similarity, and the ability to plug in custom tables/collections, regardless of their schema.
Features that currently we don't plan to port to SK are:

  • running Memory as a service
  • automatically parsing files and extracting memories
  • customizable asynchronous pipelines
  • explicit RAG implementations
  • integration with Azure AI Docum…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by dluc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
1. Q&A
Labels
None yet
2 participants