Jekyll vs Solr: What are the differences?
What is Jekyll? Blog-aware, static site generator in Ruby. Think of Jekyll as a file-based CMS, without all the complexity. Jekyll takes your content, renders Markdown and Liquid templates, and spits out a complete, static website ready to be served by Apache, Nginx or another web server. Jekyll is the engine behind GitHub Pages, which you can use to host sites right from your GitHub repositories.
What is Solr? An open source enterprise search server based on Lucene search library, with XML/HTTP and JSON APIs, hit highlighting, faceted search, caching, replication etc. Solr is the popular, blazing fast open source enterprise search platform from the Apache Lucene project. Its major features include powerful full-text search, hit highlighting, faceted search, near real-time indexing, dynamic clustering, database integration, rich document (e.g., Word, PDF) handling, and geospatial search. Solr is highly reliable, scalable and fault tolerant, providing distributed indexing, replication and load-balanced querying, automated failover and recovery, centralized configuration and more. Solr powers the search and navigation features of many of the world's largest internet sites.
Jekyll belongs to "Static Site Generators" category of the tech stack, while Solr can be primarily classified under "Search Engines".
Some of the features offered by Jekyll are:
- Simple - No more databases, comment moderation, or pesky updates to install—just your content.
- Static - Markdown (or Textile), Liquid, HTML & CSS go in. Static sites come out ready for deployment.
- Blog-aware - Permalinks, categories, pages, posts, and custom layouts are all first-class citizens here.
On the other hand, Solr provides the following key features:
- Advanced Full-Text Search Capabilities
- Optimized for High Volume Web Traffic
- Standards Based Open Interfaces - XML, JSON and HTTP
"Github pages integration" is the top reason why over 65 developers like Jekyll, while over 33 developers mention "Powerful" as the leading cause for choosing Solr.
Jekyll is an open source tool with 38.1K GitHub stars and 8.31K GitHub forks. Here's a link to Jekyll's open source repository on GitHub.
Sentry, New Relic, and Tilt are some of the popular companies that use Jekyll, whereas Solr is used by Slack, Coursera, and Zalando. Jekyll has a broader approval, being mentioned in 111 company stacks & 125 developers stacks; compared to Solr, which is listed in 140 company stacks and 42 developer stacks.
What is Jekyll?
What is Solr?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Solr?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
elastic search 와 함께 유명한 검색 엔진 오픈 소스 중 하나 이다. 처음 설정할 것이 많은데, 어플리케이션의 이해가 없다면 잦은 수정이 필요하다. Solr Client 로 제어 할 수 없고 Server 에서 설정해 줘야하는 것들이 있어 서버 설정하는 부분이 중요하다. 서버 설정만 잘 되있다면, Client 쪽 소스는 별게 없다.
중요한 건 형태소 분석기....
With limited knowledge of CSS/HTML5, Jekyll makes it easy to create templates for static HTML5 sites. Unless I really need a database for something, this is the tool I prefer for standing up websites.
I settled on Jekyll to be the CMS for my research blog. Out of the box it works, and over time I added to it... why write a dissertation when you can instead hack templates to tweak things.
This static site generator is used with "contentful-import" ruby plugin, which allows to fetch data from Contentfull and generate new web-pages based on it. Easy and fun to use.
We wanted to pay the cost for website generation up front. Doing this allows us to put our website up in AWS S3 where it can be served reliably and for cheap.
We use Jekyll to build our website. We created a collection for talks. We handle speakers and sponsors via data files.
Full text search is provided by a SOLR cluster. This is done on Master/Slave replication with Varnish as a cache.