Nov
12
2020
--

Solo.io announces service mesh platform aimed at enterprise customers

Solo.io, a Cambridge, Massachusetts service mesh startup, announced some big changes to its approach today with a full-stack platform of services aimed squarely at the enterprise. The culmination of this will be Gloo Mesh Enterprise, a new product that will be available in beta by the end of the year.

Service meshes are part of a cloud native, containerized approach to development that enable micro services to communicate with one another.

Idit Levine, founder and CEO at Solo, says that she began by creating individual components since launching the company in 2017 because she knew that it was early for service meshes. Today’s announcement is about bringing all of these components the company has created into a more coherent and connected enterprise product.

While she was worried at first that the pandemic would have a negative impact on business, she says that her company has been busier than ever and today’s announcement is really about giving customers what they have been asking for throughout this tumultuous year.

Most of Solo’s customers are running Kubernetes and they needed some missing pieces that Solo was happy to provide for them. The first problem is the primary reason the company started, which was to manage service meshes, and Gloo Mesh, which is based on the open-source Istio service mesh, helps developers manage their service mesh clusters.

Another problem involved running containers at the edge, which required an API gateway. To that end, the company announced Gloo Edge, an API gateway built on the Envoy Proxy, an edge service proxy. Running applications at the edge means they get the resources they need to improve performance and save bandwidth.

The third piece is called Gloo Portal. This provides a centralized, self-service catalog of services that developers can tap into as they are building their applications. The final piece is Gloo Extensions, which provides a way for developers to access or build extensions called web assembly modules.

All of these pieces are available as open source, but companies that want additional functionality and support and a way to connect all of these pieces will need to buy the enterprise product. Among the additional features in the enterprise version is the ability to apply roles to the APIs in Gloo Edge to control who has access. Gloo Mesh users get production Istio support including updates and patches. It also includes a dashboard for managing clusters and developer tools for building web assembly pieces in Gloo Extension.

The company has raised more than $36 million, according to PitchBook data. The most recent deal was $23 million in September. Levine says the startup has several dozen large customers at this point, and 35 employees. She said she is actively hiring and expects to be at 50 soon.

May
15
2019
--

Solo.io wants to bring order to service meshes with centralized management hub

As containers and microservices have proliferated, a new kind of tool called the service mesh has developed to help manage and understand interactions between services. While Kubernetes has emerged as the clear container orchestration tool of choice, there is much less certainty in the service mesh market. Solo.io today announced a new open-source tool called Service Mesh Hub, designed to help companies manage multiple service meshes in a single interface.

It is early days for the service mesh concept, but there are already multiple offerings, including Istio, Linkerd (pronounced Linker-Dee) and Envoy. While the market sorts itself it out, it requires a new set of tools, a management layer, so that developers and operations can monitor and understand what’s happening inside the various service meshes they are running.

Idit Levine, founder and CEO at Solo, says she formed the company because she saw an opportunity to develop a set of tooling for a nascent market. Since founding the company in 2017, it has developed several open-source tools to fill that service mesh tool vacuum.

Levine says that she recognized that companies would be using multiple service meshes for multiple situations and that not every company would have the technical capabilities to manage this. That is where the idea for the Service Mesh Hub was born.

It’s a centralized place for companies to add the different service mesh tools they are using, understand the interactions happening within the mesh and add extensions to each one from a kind of extension app store. Solo wants to make adding these tools a simple matter of pointing and clicking. While it obviously still requires a certain level of knowledge about how these tools work, it removes some of the complexity around managing them.

Solo.io Service Mesh Hub

Solo.io Service Mesh Hub (Screenshot: Solo.io)

“The reason we created this is because we believe service mesh is something big, and we want people to use it, and we feel it’s hard to adopt right now. We believe by creating that kind of framework or platform, it will make it easier for people to actually use it,” Levine told TechCrunch.

The vision is that eventually companies will be able to add extensions to the store for free, or even at some point for a fee, and it is through these paid extensions that the company will be able to make money. She recognized that some companies will be creating extensions for internal use only, and in those cases, they can add them to the hub and mark them as private and only that company can see them.

For every abstraction it seems, there is a new set of problems to solve. The service mesh is a response to the problem of managing multiple services. It solves three key issues, according to Levine. It allows a company to route the microservices, have visibility into them to see logs and metrics of the mesh and to provide security to manage which services can talk to each other.

Levine’s company is a response to the issues that have developed around understanding and managing the service meshes themselves. She says she doesn’t worry about a big company coming in and undermining her mission because she says that they are too focused on their own tools to create a set of uber-management tools like these (but that doesn’t mean the company wouldn’t be an attractive acquisition target).

So far, the company has taken more than $13 million in funding, according to Crunchbase data.

Powered by WordPress | Theme: Aeros 2.0 by TheBuckmaker.com