In Part 1 [https://clearbit-blog.ghost.io/blog/servers-part-one] of this series we gave you an overview of the deployment process at Clearbit. In this post I'm going to talk about our how we use fleet to run our services. > Note: We use Amazon's EC2 system. In this article when I refer to a machine I'm really talking about an EC2 instance. I've used machine to avoid confusion with an instance (runnning process) of an application. Life before Fleet Before migrating over to CoreOS/Fleet we were
We always get excited when there's a new easy way for people to use the Clearbit APIs. And here's the latest one! Stamplay [https://stamplay.com/?utm_medium=partner&utm_source=clearbit&utm_campaign=integrations&utm_term=clearbit&utm_content=blogpost] is a backend as a service platform that let's you add our Enrichment APIs to your application with minimal custom dev work. Using Clearbit within Stamplay is pretty simple and we wrote a quick tutorial [http://support.clearbit.com/article/105-sta
We use Docker and CoreOS extensively at Clearbit. We have over 70 different internal services running across a cluster of 18 machines on EC2. Every day our servers handle upwards of 1.5 million API calls, and that growth rate is only increasing. All this means being able to scale our infrastructure quickly is incredibly important to the company. We've made significant upfront investments into tools to help us with this and we'd like to share our experiences to help other teams facing similar ch
I'm happy to announce we've released a new data attribute for our Company API - technology tags. These tags represent the technology stack and products used by a company. This can be quite handy. We love instantly knowing whether a new signup comes from a business that already leverages cloud technology or not. In addition, it helps us be more targeted with messaging as to our prebuilt integrations (ex. someone uses Salesforce). For example the tech tags for segment.com [https://segment.com] s
There's a fair amount that's been written [https://clearbit-blog.ghost.io/blog/versioning-apis] on how to version APIs, but what nobody talks about is what goes on behind the scenes--how versioning is implemented at a code level. One reason behind this is that the implementation is often a mess, a nestled spaghetti of conditional statements littering your codebase that usually looks something like this: if params[:version] == 1 show_something else show_something_else end At Clearbit we'
Engaging stories and exclusive data, designed for our best customers. One useful issue each month.