In this post, Andy Denmark, Co-Founder and CTO of Chairish talks to us about how they’re using SignalFx to create a great shopping experience for their customers.
Chairish is an online peer-to-peer marketplace for high-end home furniture and décor. There is a web and mobile application that facilitate the buyer and seller sides of the experience.
Tell us about Chairish and your team.
Andy: Chairish is about two years old now and we are growing at a healthy rate—we have proven the model and demand for this type of service. In addition to the online marketplace, Chairish also provides the services around getting the piece safely to the buyer’s home, including logistics, payment, shipping and warranties. Most of the team here are designers, curators or marketing within home furnishing. My team is responsible for building, running and maintaining the Chairish web and mobile apps.
Tell us a little bit about the nuts and bolts of your application
Andy: Our application is made of a handful of instances on AWS, using EC2, S3, RDS, SQS, SNS, SES, ElastiCache, VPC, and Route 53.
What was changing that made you look for a monitoring tool?
Andy: When we first started, we ran the buy side on Shopify and I focused the app dev on the sell side with the listing flow, API integration to publish to Shopify and the internal tools and operational workflows to complete a transaction and get the product to the customer. We started moving off the Shopify platform as we grew and and I was building more and more components so I now needed a way to manage.
What kind of things are you monitoring?
Andy: We started with standard stuff like disk space, cpu utilization and load, Nginx timing and stats, and Elasticsearch stats. Our dashboard has evolved to also include more application level charts showing request time, memory use per request, etc.
Did you consider other tools? How did you decide on SignalFx?
Andy: One of the things I love about your approach is that it is open. Instead of closed, proprietary agents that are not well understood, you use open source collection agents that we all know well and can write to. We have built a bunch of custom stuff into our app to send metrics to SignalFx. I did look at open source tools that I have used at previous companies but shied away from building my own because there is both a visible and hidden cost. Technically I am capable of doing it but beyond the physical infrastructure costs there are hidden costs of time to deploy and manage this system to make sure it works ongoing.
Have we been useful for your team?
Andy: It’s more than just a bunch of pretty graphs, it’s a platform for me to build on top of. It is very easy for my dev team to share operations data. In my experience the way ops tools work, they create silos leading to contentious relationships between ops and dev especially when things break and the finger pointing begins. For smaller teams like mine, you’re all on the same team. SignalFx allows for easy and immediate transference of visibility and information within the team.