Feed powered byStream Blue Logo Copy 5Created with Sketch.
Algolia

Decision at Algolia about Ember.js, Rails, Discourse, Gitter, Discord, Algolia

Avatar of dzello
Developer Advocate at DeveloperMode
Ember.jsEmber.js
RailsRails
DiscourseDiscourse
GitterGitter
DiscordDiscord
AlgoliaAlgolia

Shortly after I joined Algolia as a developer advocate, I knew I wanted to establish a place for the community to congregate and share their projects, questions and advice. There are a ton of platforms out there that can be used to host communities, and they tend to fall into two categories - real-time sync (like chat) and async (like forums). Because the community was already large, I felt that a chat platform like Discord or Gitter might be overwhelming and opted for a forum-like solution instead (which would also create content that's searchable from Google).

I looked at paid, closed-source options like AnswerHub and ForumBee and old-school solutions like phpBB and vBulletin, but none seemed to offer the power, flexibility and developer-friendliness of Discourse. Discourse is open source, written in Rails with Ember.js on the front-end. That made me confident I could modify it to meet our exact needs. Discourse's own forum is very active which made me confident I could get help if I needed it.

It took about a month to get Discourse up-and-running and make authentication tied to algolia.com via the SSO plugin. Adding additional plugins for moderation or look-and-feel customization was fairly straightforward, and I even created a plugin to make the forum content searchable with Algolia. To stay on top of answering questions and moderation, we used the Discourse API to publish new messages into our Slack. All-in-all I would say we were happy with Discourse - the only caveat would be that it's very helpful to have technical knowledge as well as Rails knowledge in order to get the most out of it.

17 upvotes2 comments444 views

Decision at Algolia about React, Gatsby, Ruby, Middleman

Avatar of ronanlevesque
Software engineer at Algolia
ReactReact
GatsbyGatsby
RubyRuby
MiddlemanMiddleman

A few months ago we decided to move our whole static website (www.algolia.com) to a new stack. At the time we were using a website generator called Middleman, written in Ruby. As a team of only front-end developers we didn't feel very comfortable with the language itself, and the time it took to build was not satisfying. We decided to move to Gatsby to take advantage of its use of React , as well as its incredibly high performances in terms of build and page rendering.

8 upvotes2 comments21.7K views

Decision at Algolia about MobX, Redux.js, AngularJS, React

Avatar of proudlygeek
MobXMobX
Redux.jsRedux.js
AngularJSAngularJS
ReactReact

We started rebuilding our dashboard components using React from AngularJS over 3 years ago and, in order to have predictable client-side state management we introduced Redux.js inside our stack because of the popularity it gained inside the JavaScript community; that said, the number of lines of codes needed to implement even the simplest form was unnecessarily high, from a simple form to a more complex component like our team management page.

By switching our state management to MobX we removed approximately 40% of our boilerplate code and simplified our front-end development flow, which in the ends allowed us to focus more into product features rather than architectural choices.

7 upvotes2 comments2.1K views

Decision at Algolia about Kubernetes

Avatar of ElPicador
Staff Software Engineer at Algolia
KubernetesKubernetes

As we follow the principle of "eat your own dog food", Kubernetes was the obvious choice for us. We want our teams to handle the production of their services, and Kubernetes provides all the foundation for us to handle production on our own, without relying (too much) on our SRE team. It also allows us to auto-scale seamlessly. Today all major product - but the search API - are running on Kubernetes .

1 upvote126 views