{"id":15094,"date":"2019-05-15T19:02:28","date_gmt":"2019-05-15T19:02:28","guid":{"rendered":"https:\/\/rsoftsolution.com\/blog\/solo-io-wants-to-bring-order-to-service-meshes-with-centralized-management-hub.html"},"modified":"2019-05-15T19:02:28","modified_gmt":"2019-05-15T19:02:28","slug":"solo-io-wants-to-bring-order-to-service-meshes-with-centralized-management-hub","status":"publish","type":"post","link":"https:\/\/www.rbsitsoftwaresolution.in\/blog\/solo-io-wants-to-bring-order-to-service-meshes-with-centralized-management-hub.html","title":{"rendered":"Solo.io wants to bring order to service meshes with centralized management hub"},"content":{"rendered":"

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

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\u2019s happening inside the various service meshes they are running.<\/p>\n

Idit Levine, <\/a> 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<\/a> to fill that service mesh tool vacuum.<\/p>\n

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.<\/p>\n

It\u2019s 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.<\/p>\n

\n

Solo.io <\/a> Service Mesh Hub (Screenshot: Solo.io)<\/p>\n

\u201cThe reason we created this is because we believe service mesh is something big, and we want people to use it, and we feel it\u2019s 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,\u201d Levine told TechCrunch.<\/p>\n

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.<\/p>\n

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.<\/p>\n

Levine\u2019s company is a response to the issues that have developed around understanding and managing the service meshes themselves. She says she doesn\u2019t 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\u2019t mean the company wouldn\u2019t be an attractive acquisition target).<\/p>\n

So far, the company has taken more than $13 million in funding, according<\/a> to Crunchbase data.<\/p>\n

\n

As Kubernetes grows, a startup ecosystem develops in its wake<\/a><\/p>\n<\/blockquote>\n

\n

Article source: http:\/\/feedproxy.google.com\/~r\/techcrunchIt\/~3\/80KtAch-ns0\/<\/p>","protected":false},"excerpt":{"rendered":"

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 <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[19],"tags":[25],"class_list":["post-15094","post","type-post","status-publish","format-standard","hentry","category-enterprise-software","tag-enterprise"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t