by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Emmanuel Keller
@emmanuel-keller
Typically, QWAZR is a set of micro-services that exactly do what OpenSearchServer did as a monolith: indexing, crawling, extracting full-text, search...
OpenSearchServer 2.0 is typically a front-end over those components. It exposes a user interface and a set of JSON API. It can use the QWAZR components either embedded or distributed.
I hope those information are useful if you were wondering what the hell we were doing :D
tmikaeld
@tmikaeld
@emmanuel-keller Thanks a ton for the info, that's SUPER exciting! We currently use opensearchserver wrapped in JS as a very fast search for websites.
So we will certainly need this if we are going to scale up
Emmanuel Keller
@emmanuel-keller
@tmikaeld Great ! We will try to make the move as smooth than possible. There will be documentation about that.
tmikaeld
@tmikaeld
@emmanuel-keller Super! Can you also make it possible to set any origin on the API? Right now we proxy from a local node server and it seems like a unnessesary step.
Emmanuel Keller
@emmanuel-keller
@tmikaeld Yes, we implemented https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS in 2.0
tmikaeld
@tmikaeld
Sweeeeet!!
Thanks :-D
tmikaeld
@tmikaeld
@emmanuel-keller When is 2.0 going to be released you think?
tmikaeld
@tmikaeld
@emmanuel-keller Hm, is this like serverless architecture? Seems similar
All of this seems like a very ambitious project
We are currently moving many projects to serverless workers, due to the scalability and security of it
And of course price-savings
Emmanuel Keller
@emmanuel-keller
Yes, the new Saas infrastructure will be a serverless offer.
tmikaeld
@tmikaeld
So this makes it possible to setup our own serverless servers?
Or is that only for your cloud variant?
Emmanuel Keller
@emmanuel-keller
Everything is open sourced. So, you can build your own infrastructure
tmikaeld
@tmikaeld
Wow, that's really generous
How come you made it open source?
No license fee to use it?
Emmanuel Keller
@emmanuel-keller
We will provide Docker images for each components
we think about providing a dedicated documentation platform for partners and distributors
We are happy to provide our tools to the community, but even more happy if we can build a nice ecosystem together
The current support services will evolve to something more simple. Probably an access to a common knowledge base, available for paying user only.
Do you think it makes sense ?
tmikaeld
@tmikaeld
Yes, something like the model proxmox uses
Then even us single-person companies can get involved without breaking the bank
Bernard
@Nanard
Hi, @emmanuel-keller thanks you for the information about users. I will try it asap.
@emmanuel-keller For your information, when you compile v 2.x it's impossible to run it. I had to change the mainClass in the pom.xml : From : <mainClass>com.jaeksoft.searchlib.Server</mainClass> to <mainClass>com.jaeksoft.opensearchserver.Server</mainClass>
Emmanuel Keller
@emmanuel-keller
@Nanard, we just report your fix. The class name was the one from 1.5, Thanks !
tmikaeld
@tmikaeld
@emmanuel-keller When do you think 2.x will be production ready?
Emmanuel Keller
@emmanuel-keller
@tmikaeld It will be beta in September and production ready in October. The low level components (the Qwazr suite) is already stable and used in few really visible projects. We are building the user interface that bring those components together.
tmikaeld
@tmikaeld
@emmanuel-keller Superb! I've marked a couple of days at the start of October for testing, I have really high hopes for this platform :-)
@emmanuel-keller How does Qwazr handle API endpoints, do we need our own API gateway in front of it?
Emmanuel Keller
@emmanuel-keller
The Qwazr components are low level specialized modules that can be used as microservices or embedded in a Java applications. They exposes primitives API.
tmikaeld
@tmikaeld
In other words, a loadbalancer + gateways is needed.
Emmanuel Keller
@emmanuel-keller
The OpenSearchServer layer will simplify everything. It will provide a user interface as well as high level API. It will also hide the complexity by providing a set of vertical API who will handle typical use cases. Web search, entreprise search, data analytics...
Exactly. It will be possible to setup several instances of OpenSearchServer by putting a load balancer. That’s typically a good idea to put the SSL handling on this layer. On our SaaS platform we use Nginx for that purpose.
tmikaeld
@tmikaeld
Great! You mentioned it working like a serverless architecture, i guess you didn't mean FAAS then?
Emmanuel Keller
@emmanuel-keller
The Qwazr components can also run in dedicated servers. To handle the scalability without having to change the front-end. OpenSearchServer can either use the Qwazr components embedded or externalized.
Well.. in the future, we may expose the Qwazr components individually thru our Saas platform. Which will change the idiom to Faas...
But in thing after the other :smile:
One thing..
tmikaeld
@tmikaeld
Of course, I'm excited either way to see opensearchserver progressing into a new scalable platform!
Emmanuel Keller
@emmanuel-keller
We probably will provide beta access to our future partners.
That’s great. The testing access will remain free for you to be able to test it and provide feedback. Our focus is now performances and simplicity.
tmikaeld
@tmikaeld
Hey! It looks like opensearchserver has been put on ice for a while?
Emmanuel Keller
@emmanuel-keller
Hi there ... the ice is melting ...