Effx, a startup that aims to provide developers with a better view of their microservice architectures, today announced that it has raised a $ 3.9 million round of funding led by Kleiner Perkins and Cowboy Ventures. Other investors and angels in this round include Tokyo Black, Essence VC Fund, Jason Warner, Michael Stoppelman, Vijay Pandurangan and Miles Grimshaw.
The company's founder and CEO, Joey Parsons, was one of the first employees of Rackspace and then first I went to Flipboard and then Airbnb a few years ago, where he created the company's site reliability team.
"When I joined Airbnb for the first time, it's mid-2015, it's already a unicorn, already a well-known entity in the industry, but they didn't have anyone there who really took care of the cloud infrastructure and reliability there [...], "he told me. The original Airbnb platform was built on Ruby on Rails and was no longer able to adapt to the needs of the growing platform. "Me and a lot of people who were really smarter than me on the team got together and decided at that point, 'okay, let's break this monolith or monorail that we call it and divide it into microservices.' "
But microservices obviously present their challenges - after all they constantly change and those changes are reflected in different UI - and it is essentially from there that the idea of Effx was born. The idea behind the product is to provide engineers with a single glass panel to get all the information they need about the microservices that have been distributed in their organization.
On Airbnb, the Parsons team created a small metastore to keep track of what each service did, who owned it, in what language it was written and if, for example, it fell within the scope of the PCI or GDPR. After leaving Airbnb, Parsons went to Kleiner as a resident entrepreneur and started working on developing this idea of bringing some of the ideas on what the team built on Airbnb to multiple companies. He collected a small amount of money from Kleiner to hire the initial design team in 2019 and then started testing the product with a first group of pilot customers earlier this year.
In its early iterations, the product was based on engineers who wrote YAML files, which the product could then consume, but few engineers love writing YAML files and the value of a tool like this comes from the ability to automate much of this work. Then the team developed integrations with common service orchestration platforms, including Kubernetes, but also AWS Lambda and ECS.
"What we've found is that most companies that have moved to microservices use a combination of those platforms - maybe one, maybe two, maybe all three - to orchestrate things," explained Parsons. "So we integrated very heavy integrations into those platforms where in Kubernetes we can drag a client there, automatically discover all your services, populate as much as possible in the catalog and then do the same thing for a Lambda AWS or ECS perspective in which we consume data from those platforms and enter the data. "
As noted by Parsons, the value here is not only to get that single glass pane, but once you have all this information and dependencies of these services and combine them with your CI / CD data, it also becomes a new tool. for troubleshooting since it helps you see which services changed before something broke. To enable this even better, teams can add links to their runbooks, documentation and version control tools.
Parsons tells me that the team is currently in the process of closing more drivers and hiring more engineers as it works to develop its service, add more integrations and find new ways to help its customers use all the data they collect.
"As the future of what we are building comes true, the most important thing for us right now is to truly offer the value that our existing product offers our end users as a platform for building more business," he explained. Parsons. "I think in the long run, the power of this feed and the data recovery behind it ends up being a really interesting way for us simply because there are many great insights you can build for organizations based on patterns and the cadence of information that appears in this feed, to help teams really understand why there is that incident that happens every Tuesday at midnight UTC. "
