Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Peter Bourgon
Observability in 5 minutes. Plus, the best 20 observability software vendors
August 16, 2021 by Hayden James, in Blog Linux In just a little over a year, we’ve covered the future of APM (application performance monitoring) and the expansion of APM into observability. Followed by the race between software vendors to define observability. Most recently, we looked at the evolution of observability as shared by industry-leading software vendors. This article will be answering the following questions to bring clarity to the topic of observability: What is observability?
State at the Edge: an Interview with Peter Bourgon
InfoQ Homepage Articles State at the Edge: an Interview with Peter Bourgon Key Takeaways Latency is the biggest reason that a general purpose database isn’t a good fit for edge architectures. CRDTs, or conflict-free replicated data types, are a relatively novel state primitive that give us a way to skirt around a lot of the complexity around consistency.
Infinite Parallel Universes: State at the Edge
Transcript Bourgon: This is my silly talk with all these cool science pictures on it. Before you ask, they don't mean anything but I do feel like they give my talk a little bit of gravitas so I hope you'll take that into consideration. This is going to be like a walkthrough of a system that I'm researching and prototyping and building and have been for a little while.
Peter Bourgon on CRDTs and State at the Edge
InfoQ Homepage Podcasts Peter Bourgon on CRDTs and State at the Edge Today on The InfoQ Podcast, Wes Reisz talks with Peter Bourgon. Peter is a distributed system engineer working at Fastly. His area of interest is around coordination free replicated systems. The two engineers talk about the space of Conflict-Free Replicated Data Types (CRDTs) specifically in the context of edge compute.
Peter Bourgon · Go naming tips
2019 04 24 (This post adapted from a Twitter thread.) In my experience, the best way to name types in Go is as follows: Structs are plain nouns: API, Replica, Object Interfaces are active nouns: Reader, Writer, JobProcessor Functions and methods are verbs: Read, Process, Sync Besides being consistent, this model has two nice secondary benefits. First, doc comments become natural and fluent. // Sync the local replica state to the provided upstream. func (r *Replica) Sync(u Upstream) error { ...
Three Productive Go Patterns to Put on Your Radar | Blog | AppDynamics
By most definitions, with just 26 keywords, a terse spec, and a commitment to orthogonal features, Go is a simple language. Go programmers are expected to use the basic building blocks offered by the language to compose more complex abstractions. Over time, best-in-class solutions to frequently encountered problems tend to be discovered, shared, and replicated.
Metrics, tracing, and logging
Today I had the good fortune of attending the 2017 Distributed Tracing Summit, with lots of rad folks from orgs like AWS/X-Ray, OpenZipkin, OpenTracing, Instana, Datadog, Librato, and many others I regret that I’m forgetting. At one point the discussion took a turn toward project scope and definitions. Should a tracing system also manage logging? What indeed is logging, when viewed through the different lenses represented in the room?
6年間におけるGoのベストプラクティス | プログラミング | POSTD
（本稿は、QCon London 2016で行った講演の内容に基づいています。スライドとビデオは近日中に掲載予定です） 2014年に開催された最初のGopherConで、私は「Best Practices in Production Environments（本番環境でのベストプラクティス）」と題した講演を行いました。SoundCloudの私たちはGoのアーリーアダプターで、その時点までに既に2年近く、本番環境向けの様々なGoコードを書き、実行し、メンテナンスしていました。そして私たちはいくつかのことを学んだので、その教訓をまとめ、多くの人に伝えたいと思ったのです。 それ以来、私はフルタイムでGoを使う仕事を続けています。SoundCloudではその後の活動やインフラチームで、そして現在はWeaveworksでWeave ScopeやWeave Meshの開発に使っています。また、オープンソースのマイクロサービス向けツールキットGo...
Go best practices, six years in
In 2014, I gave a talk at the inaugural GopherCon titled Best Practices in Production Environments. We were early adopters at SoundCloud, and by that point had been writing, running, and maintaining Go in production in one form or another for nearly 2 years. We had learned a few things, and I tried to distill and convey some of those lessons.
Video Tutorial: Weave Scope, the Missing Piece to Show What You've Built with Docker
A few weeks ago on The New Stack, Weaveworks software engineers Peter Bourgon and David Kaltschmidt published a tutorial on Weave Scope, which provides for automatic detection and monitoring of every host, container and process in your infrastructure, and builds a map of their communication. Recently, The New Stack Founder Alex Williams connected with Peter and the Weaveworks team to capture this video tutorial of Scope, and to discuss the development of this new product.
Now in Beta, Rancher Labs Runs Docker Natively in Production
Rancher Labs is releasing the beta of its management platform to run Docker containers in production. It comes after raising a $10 million round last week from the Mayfield Fund. Rancher is a reflection of a transitionary time to a more purpose-built infrastructure, designed for a new application era that still has some way to go. Rancher offers a way to manage Docker in production. Everything in Rancher is a container. It is meant to make developing apps easier for the developer.
Docker's New Microservices Monitoring Program Looks Like an OS-Style Approach
Docker is a container host, a multitude of corrections tell us, and not an operating system. But the “container host” took another huge step towards looking like an operating system, as Docker Inc. officially launched this week the first in what appear to be several ecosystem technology partner programs, this one geared toward certifying monitoring systems. With a partner program, third parties build their supporting products to a specification published by the supporting party.
How To Detect, Map and Monitor Docker Containers with Weave Scope from Weaveworks
If you use Docker, you probably already know about Weave’s Docker network. Weave creates a virtual, software-defined network, or SDN, across every Docker host in your infrastructure. Each container gets its own IP, allowing you to design your application topology without changing your application’s behavior. Weave Run, a set of companion tools for service discovery and address management, also contributes to an easier development experience.
Why the Redis Ecosystem is Flourishing
The in-memory, key-value data store Redis continues to consolidate its market position as more applications seek to use the open source project as a data structure server for on-the-spot, real-time application processing.
Go: Best Practices for Production Environments
(This was originally a talk at GopherCon 2014. Find the slides here, and the video here.) (This article has been updated for 2016.) At SoundCloud, we structure our product as an API with many clients. That is, our main website, mobile client, and mobile apps are all first-order clients of a single main API. Behind that API is a universe of services: SoundCloud operates basically as a Service-Oriented-Architecture. We’re also a polyglot organization, which means we use lots of languages.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Peter
Contact Peter, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack