Content
ADAM goes Elastic
May 11, 2015
On April 22 and 23, ADAM software, a leader in the Forrester wave of digital asset management, held its yearly event called “ADAM Sync” in Europe. The ideal occasion to be immersed in company insights and future roadmaps, and in creative ideas presented by the different speakers.
This is part 2 discussing the technical track of the ADAM Sync event.
Content
As the title of the post suggests: ADAM goes for Elastic. This means the platform will have a completely redesigned search engine, no longer based upon Microsoft SQL Server, but based upon Elastic (formerly know as Elasticsearch). Elastic is a search server based on Lucene. It provides a distributed, multitenant-capable full-text search engine with a RESTful web interface and schema-free JSON documents. Shay Banon released the first version of Elasticsearch in 2010. In 2012 Elasticsearch BV was founded to provide commercial solutions around the product. Since then Elastic has become one of the most significant search engines available on the market, with a better and newer architecture than its counterpart Apache SOLR.
Elastic introduces modern search features such as autocorrection, thesaurus and more Google like features such as “Did you mean…?”. ADAM will now support the “CONTAINS” operator in searches, something that was often asked by customers but couldn’t be handled by SQL Server Full Text engine.
By using Elastic, ADAM can offload the SQL Server resulting in an overall performance gain. Several tests confirmed that the overall search queries take up significantly less time to be executed. Currently only records, files and fields will be driven by Elastic, search on classifications and other system objects will be kept on the SQL Server. The security mechanisms and caches of Elastic will be used. This allows ADAM to “drop” existing security caches that were based upon SQL Server, resulting in another performance boost and lower memory requirements on the ADAM Server itself.
The second important feature being introduced is a REST based API, making all common ADAM functionality available by means of platform independent HTTP calls. This API will become the first in line to use. The .NET API will continue to exist, but will serve for tasks REST is less suited for. An example of this are bulk record operations.
We can expect both features to become available this year in ADAM 5.x versions of the product.
Some indications and hints were given on the new major version: ADAM 6. The new version needs to become a more unified platform where studios will be merged into one application, serving different roles of users by means of the same UI. It results in a more unified “Smart Content Hub” experience.
If you are (also) interested in the main summary of the Sync event, than you should also read part 1: Welcome, Smart Content Hub!.
Your Privacy
Strictly Necessary Cookies
Performance Cookies
Targeting Cookies
Privacy Preference Center
Your Privacy
When you visit any web site, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not directly identify you, but it can give you a more personalised web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
Strictly Necessary CookiesAlways Active
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
Performance CookiesAlways Active
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Please be informed that Hubspot, in its capacity of service provider, collects your data on an anonymized basis. If you however submit a form via Hubspot, you acknowledge and agree that your personal data will be used for marketing purposes.
Targeting Cookies
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Please be informed that Hubspot, in its capacity of service provider, collects your data on an anonymized basis. If you however submit a form via Hubspot, you acknowledge and agree that your personal data will be used for marketing purposes.
When you withdraw your consent, we will not load the targeting scripts anymore. New tracking will thus not be captured anymore. To remove what was captured before your withdrawal, you need to remove those cookies manually yourself through your browser.