PageSourceSearch

https://weaviate.io/assets/js/421c0d42.d5b4b340.js

js weaviate.io collected 2026-10-01 08:40:31 UTC 13,033 bytes, 1 lines download raw bytes

1"use strict";(globalThis.webpackChunkmy_website=globalThis.webpackChunkmy_website||[]).push([[10759],{88440(e,i,t){t.r(i),t.d(i,{assets:()=>h,contentTitle:()=>l,default:()=>u,frontMatter:()=>r,metadata:()=>a,toc:()=>c});var a=t(64076),n=t(74848),o=t(28453),s=t(73284);const r={title:"What to expect from Weaviate in 2023",slug:"what-to-expect-from-weaviate-in-2023",authors:["etienne"],date:new Date("2023-02-14T00:00:00.000Z"),tags:["engineering"],image:"./img/hero.png",description:"Learn about the six pillars outlining how Weaviate will evolve in 2023."},l=void 0,h={image:t(35444).A,authorsImageUrls:[void 0]},c=[{value:"The Six Pillars for 2023",id:"the-six-pillars-for-2023",level:2},{value:"Ingestion and Search Pipelines",id:"ingestion-and-search-pipelines",level:3},{value:"Beyond Billion Scale: Large-Scale Performance",id:"beyond-billion-scale-large-scale-performance",level:3},{value:"Cloud Operations & Scaling",id:"cloud-operations--scaling",level:3},{value:"New Vector Indexes",id:"new-vector-indexes",level:3},{value:"Improving our Client and Module Ecosystem",id:"improving-our-client-and-module-ecosystem",level:3},{value:"Community",id:"community",level:3},{value:"Conclusion: Proud of how far we\u2019ve come, excited about the future",id:"conclusion-proud-of-how-far-weve-come-excited-about-the-future",level:2},...s.RM];function d(e){const i={a:"a",code:"code",h2:"h2",h3:"h3",img:"img",p:"p",...(0,o.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(i.p,{children:(0,n.jsx)(i.img,{alt:"What to expect from Weaviate in 2023",src:t(73295).A+"",width:"1800",height:"946"})}),"\n",(0,n.jsx)(i.p,{children:"Without a doubt, 2022 has been the most exciting year for Weaviate so far. The company and the product have grown tremendously, and we are incredibly excited about 2023. Weaviate\u2019s usage numbers are through the roof, and so are your feedback and requests for what you\u2019re still missing from Weaviate."}),"\n",(0,n.jsx)(i.p,{children:"In this blog post, I will introduce you to the six pillars outlining how Weaviate will get even better in 2023. Weaviate development is highly dynamic \u2013 we don\u2019t waterfall-plan for the entire year \u2013 but nevertheless, we want to give you the best possible overview of what to expect in the coming year."}),"\n",(0,n.jsx)(i.h2,{id:"the-six-pillars-for-2023",children:"The Six Pillars for 2023"}),"\n",(0,n.jsx)(i.h3,{id:"ingestion-and-search-pipelines",children:"Ingestion and Search Pipelines"}),"\n",(0,n.jsxs)(i.p,{children:[(0,n.jsx)(i.img,{alt:"Ingestion and Search Pipelines",src:t(80968).A+"",width:"1600",height:"1020"}),"\nWeaviate\u2019s strong and growing module ecosystem gives you plenty of flexibility. Whether you use Weaviate as a pure vector search engine or with the addition of vectorizer, reader, and generator modules, you can always configure it to your liking. In early 2023 we even saw the addition of the ",(0,n.jsx)(i.a,{href:"https://docs.weaviate.io/weaviate/model-providers/openai/generative",children:(0,n.jsx)(i.code,{children:"generative-openai"})})," module (with other generative modules to come)."]}),"\n",(0,n.jsxs)(i.p,{children:["We want to give you even more flexibility in combining these steps this year. You can control arbitrary querying steps through the ",(0,n.jsx)(i.a,{href:"https://github.com/weaviate/weaviate/issues/2560",children:"proposed Pipe API"}),", such as reading, re-ranking, summarizing, generating, and others. Similarly, we want to give you more flexibility during ingestion time: how about ",(0,n.jsx)(i.a,{href:"https://github.com/weaviate/weaviate/issues/2509",children:"extracting PDFs"})," or applying ",(0,n.jsx)(i.a,{href:"https://github.com/weaviate/weaviate/issues/2439",children:"stemming"})," to your BM25 and hybrid search?"]}),"\n",(0,n.jsx)("br",{}),"\n",(0,n.jsx)(i.h3,{id:"beyond-billion-scale-large-scale-performance",children:"Beyond Billion Scale: Large-Scale Performance"}),"\n",(0,n.jsx)(i.p,{children:(0,n.jsx)(i.img,{alt:"Billion Scale",src:t(44177).A+"",width:"1600",height:"1020"})}),"\n",(0,n.jsxs)(i.p,{children:["In 2022, we published the ",(0,n.jsx)(i.a,{href:"/blog/sphere-dataset-in-weaviate",children:"Sphere Demo Dataset for Weaviate"}),". This marked the first time (to our knowledge) that more than a billion objects and vectors were imported into Weaviate. Dealing with ever-growing datasets is not only about being able to handle their size. Our users run complex queries in production and often have strict latency requirements. This pillar is all about performance. The first big step will be the move towards a ",(0,n.jsx)(i.a,{href:"https://github.com/weaviate/weaviate/issues/2511",children:"Native Roaring Bitmap Index"}),". In the most extreme case, this new index time can speed up filtered vector search ",(0,n.jsx)(i.a,{href:"https://twitter.com/etiennedi/status/1621180981519458305",children:"by a factor of 1000"}),".  But it doesn\u2019t stop there; we are already thinking about the next steps. Whether you want faster aggregations or new types of specialized indexes, we will ensure you can hit all your p99 latency targets with Weaviate."]}),"\n",(0,n.jsx)("br",{}),"\n",(0,n.jsx)(i.h3,{id:"cloud-operations--scaling",children:"Cloud Operations & Scaling"}),"\n",(0,n.jsx)(i.p,{children:(0,n.jsx)(i.img,{alt:"cloud operations scaling",src:t(51673).A+"",width:"1600",height:"1020"})}),"\n",(0,n.jsxs)(i.p,{children:["When we introduced ",(0,n.jsx)(i.a,{href:"https://docs.weaviate.io/weaviate/concepts/replication-architecture",children:"Replication"})," to Weaviate in late 2022, we celebrated a significant milestone. It\u2019s never been easier to achieve a highly available setup, and you can even dynamically scale your setup to increase throughput. 2023 is all about improving your cloud and operations experience. We will give you more control over ",(0,n.jsx)(i.a,{href:"https://github.com/weaviate/weaviate/issues/2586",children:"how to structure your workloads"})," in a distributed setup and more ",(0,n.jsx)(i.a,{href:"https://github.com/weaviate/weaviate/issues/2228",children:"flexibility to adapt to your ever-changing needs"}),". And, of course, we\u2019re constantly working on making your distributed cluster ",(0,n.jsx)(i.a,{href:"https://github.com/weaviate/weaviate/issues/2405",children:"even more resilient"}),"."]}),"\n",(0,n.jsxs)(i.p,{children:["Speaking of Cloud, arguably the easiest way to spin up a new use case with Weaviate is through the ",(0,n.jsx)(i.a,{href:"/pricing",children:"Weaviate Cloud"}),"."]}),"\n",(0,n.jsx)("br",{}),"\n",(0,n.jsx)(i.h3,{id:"new-vector-indexes",children:"New Vector Indexes"}),"\n",(0,n.jsx)(i.p,{children:(0,n.jsx)(i.img,{alt:"vector indexes",src:t(36769).A+"",width:"1200",height:"766"})}),"\n",(0,n.jsxs)(i.p,{children:["Last year we gave you a sneak peek into our ",(0,n.jsx)(i.a,{href:"/blog/ann-algorithms-vamana-vs-hnsw",children:"Vector Indexing Research"}),", and this year you will be able to try out new vector indexes for yourself. Since the beginning, Weaviate has supported vector indexing with ",(0,n.jsx)(i.a,{href:"https://docs.weaviate.io/weaviate/concepts/vector-index",children:"HNSW"}),", which leads to ",(0,n.jsx)(i.a,{href:"https://docs.weaviate.io/weaviate/benchmarks/ann",children:"best-in-class query times"}),". But not every use case requires single-digit millisecond latencies. Instead, some prefer cost-effectiveness. Due to its relatively high memory footprint, HNSW is only cost-efficient in high-throughput scenarios. However, HNSW is inherently optimized for in-memory access. Simply storing the index or vectors on disk or memory-mapping the index kills performance."]}),"\n",(0,n.jsx)(i.p,{children:"This is why we will offer you not just one but two memory-saving options to index your vectors without sacrificing latency and throughput. In early 2023, you will be able to use Product Quantization, a vector compression algorithm, in Weaviate for the first time. We are already working on a fully disk-based solution which we will release in late 2023."}),"\n",(0,n.jsx)("br",{}),"\n",(0,n.jsx)(i.h3,{id:"improving-our-client-and-module-ecosystem",children:"Improving our Client and Module Ecosystem"}),"\n",(0,n.jsx)(i.p,{children:(0,n.jsx)(i.img,{alt:"client modules",src:t(20678).A+"",width:"1600",height:"1020"})}),"\n",(0,n.jsxs)(i.p,{children:["So far, we have only discussed features related to Weaviate Core, the server in your setup. But the Weaviate experience is more than that. Modules allow you to integrate seamlessly with various embedding providers, and our language clients make Weaviate accessible right from your application. This year, we will further improve both. This includes ",(0,n.jsx)(i.a,{href:"https://github.com/weaviate/weaviate-python-cl
1ient/issues/205",children:"improved APIs"})," on the client side, new modules, for example, for ",(0,n.jsx)(i.a,{href:"https://docs.weaviate.io/weaviate/model-providers/openai/generative",children:"generative search"}),", and improvements to our existing modules."]}),"\n",(0,n.jsx)("br",{}),"\n",(0,n.jsx)(i.h3,{id:"community",children:"Community"}),"\n",(0,n.jsx)(i.p,{children:(0,n.jsx)(i.img,{alt:"community",src:t(9520).A+"",width:"1600",height:"1020"})}),"\n",(0,n.jsx)(i.p,{children:"The most important pillar is all of you \u2013 our community. This includes both free, open-source users that self-host their Weaviate setup, as well as paid enterprise users and anyone using our Weaviate-as-a-Service offerings. We value your feedback and love that you are part of shaping our future."}),"\n",(0,n.jsxs)(i.p,{children:["Last year we introduced our ",(0,n.jsx)(i.a,{href:"https://docs.weaviate.io/weaviate/roadmap",children:"dynamic roadmap page"})," that allows you to create and upvote your favorite feature requests. This way, you can make sure that your voice is heard, and we can see what all of you need the most."]}),"\n",(0,n.jsx)("br",{}),"\n",(0,n.jsx)(i.h2,{id:"conclusion-proud-of-how-far-weve-come-excited-about-the-future",children:"Conclusion: Proud of how far we\u2019ve come, excited about the future"}),"\n",(0,n.jsx)(i.p,{children:"In the beginning, I mentioned that not just the product but also the company grew significantly last year. I am incredibly proud of what we have achieved \u2013 both overall and in the past year. This wouldn\u2019t have been possible without an absolutely fantastic team. Everyone working on Weaviate \u2013 whether a full-time employee or open-source contributor \u2013 is doing a fantastic job. I am proud of you all and highly excited about the future. Thank you all, and let\u2019s make 2023 the most exciting year for Weaviate users so far!"}),"\n",(0,n.jsx)("br",{}),"\n","\n",(0,n.jsx)(s.Ay,{})]})}function u(e={}){const{wrapper:i}={...(0,o.R)(),...e.components};return i?(0,n.jsx)(i,{...e,children:(0,n.jsx)(d,{...e})}):d(e)}},35444(e,i,t){t.d(i,{A:()=>a});const a=t.p+"assets/images/hero-a265180e072e898271ada023a0a59d57.png"},44177(e,i,t){t.d(i,{A:()=>a});const a=t.p+"assets/images/billion-scale-fce780af8410ea22c39c1461aece9556.png"},20678(e,i,t){t.d(i,{A:()=>a});const a=t.p+"assets/images/client-modules-92947b93a3244d0704227fe4c7e221a8.png"},51673(e,i,t){t.d(i,{A:()=>a});const a=t.p+"assets/images/cloud-operations-scaling-3b41b8192be76a1d8f53efe3fe124db8.png"},9520(e,i,t){t.d(i,{A:()=>a});const a=t.p+"assets/images/community-a843768b9a1850772fc5e5b0a45d7db1.png"},73295(e,i,t){t.d(i,{A:()=>a});const a=t.p+"assets/images/hero-a265180e072e898271ada023a0a59d57.png"},80968(e,i,t){t.d(i,{A:()=>a});const a=t.p+"assets/images/search-pipeline-03ca7defbf80a1ef0adf9cba372b4410.png"},36769(e,i,t){t.d(i,{A:()=>a});const a=t.p+"assets/images/vector-indexes-74b67108a590c07ec93896d1ec0ce2b1.png"},64076(e){e.exports=JSON.parse('{"permalink":"/blog/what-to-expect-from-weaviate-in-2023","editUrl":"https://github.com/weaviate/weaviate-io/tree/main/blog/2023-02-14-what-to-expect-from-weaviate-in-2023/index.mdx","source":"@site/blog/2023-02-14-what-to-expect-from-weaviate-in-2023/index.mdx","title":"What to expect from Weaviate in 2023","description":"Learn about the six pillars outlining how Weaviate will evolve in 2023.","date":"2023-02-14T00:00:00.000Z","tags":[{"inline":true,"label":"engineering","permalink":"/blog/tags/engineering"}],"readingTime":5.42,"hasTruncateMarker":true,"authors":[{"name":"Etienne Dilocker","title":"CTO","url":"https://github.com/etiennedi","imageURL":"/img/people/icon/etienne.jpg","key":"etienne","page":null}],"frontMatter":{"title":"What to expect from Weaviate in 2023","slug":"what-to-expect-from-weaviate-in-2023","authors":["etienne"],"date":"2023-02-14T00:00:00.000Z","tags":["engineering"],"image":"./img/hero.png","description":"Learn about the six pillars outlining how Weaviate will evolve in 2023."},"unlisted":false,"prevItem":{"title":"Combining LangChain and Weaviate","permalink":"/blog/combining-langchain-and-weaviate"},"nextItem":{"title":"Weaviate Podcast Search","permalink":"/blog/weaviate-podcast-search"}}')}}]);

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.