サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
Wikipedia
eng.yammer.com
At Yammer, any developer can ship any service to any environment with a single click. Any developer can deploy changes to any of the services that power Yammer.com, without having to be an expert in that service. How? We built something called Deploymacy, the central hub for all deployment activities at Yammer. Our role as engineers at the end of the day is to provide business value. The faster we
TL;DR: We’ve built a lazy mirror to smooth over the official npm repository going down. When your continuous integration and deployment systems use npm to install modules, you need to take steps to make sure it’s available when you need it. And like everything on the internet, perfect uptime is not something you can guarantee. There are a few options here… Commit all your modules to version contro
This is an overview of the process, takeaways, gotchyas, and hopefully useful persnickety details of how Yammer went about sharding its legacy rails app running on Postgresql. I’ll briefly cover what sharding is and what problems it addresses, but there are many other readily available resources describing it in more detail (Wikipedia, CodeFutures, lmgtfy) Why sharding? The impetus behind sharding
The node community has seen a lot of discussion recently about managing dependencies with npm. In particular, people are debating the merits of using npm for deploying production applications. Mikeal Rogers's post, about checking modules dependencies into version control, sparked much of the discussion. Everyone has opinions, and certainly everyone's deployment concerns are different. I thought it
Earlier this week, a private email I wrote to Donald Fischer and Martin Odersky was leaked and a surprising amount of controversy ensued. The fact that I described some of our team's negative experiences with Scala was misrepresented by some as constituting an official Yammer position or announcement. It was not; it was a private email. This is Yammer's official position on the subject: our goal
When I started at Yammer, Adam (our CTO and mascot) and I sat down and worked out a rough architectural roadmap for Yammer. High on our list was a stable, scalable system for the realtime (i.e., sub-second latency) delivery of messages for two major reasons: user experience and operational efficiency. First, part of our World Domination Plan is to extend Yammer to include conversations of all type
このページを最初にブックマークしてみませんか?
『Yammer Engineering』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く