In May 2019, Amalgam Insights attended Knowledge 2019, ServiceNow’s annual end-user conference. Since ServiceNow’s founding in 2004, the company has evolved from its roots as an IT asset and service management company to a company that supports digital workflow across IT, HR, service, and finance with the goal of making work better for every employee. In attending this show, Amalgam Insights was especially interested in seeing how ServiceNow was evolving its message to reflect what Amalgam Insights refers to as “Market Evolvers,” companies that have gained market dominance in their original market and taken advantage of modern mobile, cloud, and AI technology to expand into other markets. (Examples of Market Evolvers include, but are not excluded to, Salesforce, ServiceNow, Workday, Informatica, and Tangoe.) Continue reading “Knowledge 2019 and ServiceNow’s Vision for Transforming the World of Work”
Amalgam Insights has just published my highly anticipated SmartList Market Guide on Service Mesh. It is currently available this week at no cost as we prepare for KubeCon and CloudNativeCon Europe 2019 where I’ll be attending.
Before you go to the event, get prepared by catching up on the key strategies, trends, and vendors associated with microservices and service mesh. For instance, consider how the Service Mesh market is currently constructed.
To get a deep dive on this figure regarding the three key sectors of the Service Mesh market, gain insights describing the current State of the Market for service mesh, and learn where key vendors and products including Istio, Linkerd, A10, Amazon, Aspen Mesh, Buoyant, Google, Hashicorp, IBM, NGINX, Red Hat, Solo.io, Vamp, and more fit into today’s microservices management environment, download my report today.
On April 2, 2019, Amalgam Insights Research Fellow Tom Petrocelli published Technical Guide: A Service Mesh Primer, which serves as a vital starting point for technical architects and developer teams to understand the current trends in microservices and service mesh. This report provides enterprise architects, CTOs, and developer teams with the guidance they need to understand the microservices architecture, service mesh architecture, and OSI model context necessary to conceptualize service mesh technologies.
In this report, Amalgam Insights provides context in the following areas: Continue reading “Tom Petrocelli Releases Groundbreaking Technical Guide on Service Mesh”
In early January, I started researching the service mesh market. To oversimplify, a service mesh is a way of providing for the kind of network services necessary for enterprise applications deployed using a microservices architecture. Since most microservices architectures are being deployed within containers and, most often, managed and orchestrated using Kubernetes, service mesh technology will have a major impact on the adoption of these markets.
As I began writing the original paper, I quickly realized that an explanation of service mesh technology was necessary to understand the dynamic of the service mesh market. Creating a primer on service mesh and a market guide turned out to be too much for one paper. It was unbearably long. Subsequently, the paper was split into two papers, a Technical Guide and a Market Guide.
The Technical Guide is a quick primer on service mesh technology and how it is used to enhance microservices architectures, especially within the context of containers and Kubernetes. The Market Guide outlines the structure of the market for service mesh products and open source projects, discusses many of the major players, and talks to the current Istio versus Linkerd controversy. The latter is actually a non-issue that has taken on more importance than it should given the nascence of the market.
The Technical Guide will be released next week, just prior to Cloud Foundry Summit. Even though service mesh companies seem to be focused on Kubernetes, anytime there is a microservices architecture, there will be a service mesh. This is true for microservices implemented using Cloud Foundry containers.
The Market Guide will be published roughly a month later, before Red Hat Summit and KubeCon+CloudNative Summit Europe, which I will be attending. Most of the vendors discussed in the Market Guide will be in attendance at one or the other conference. Read the report before going so that you know who to talk to if you are attending these conferences.
A service mesh is a necessary part of emerging microservices architectures. These papers will hopefully get you started on your journey to deploying one.
Note: Vendors interested in leveraging this research for commercial usage are invited to contact Lisa Lincoln (email@example.com).
DevOps Research Fellow Tom Petrocelli has just published a new report describing the roles that Cloud Foundry Application Runtime and Kubernetes play in supporting microservices. This report explores when each solution is appropriate and provides a set of vendors that provide resources and solutions to support the development of these open source projects.
Organizations and Vendors mentioned include: Cloud Foundry Foundation, Cloud Native Computing Foundation, Pivotal, IBM, Suse, Atos, Red Hat, Canonical, Rancher, Mesosphere, Heptio, Google, Amazon, Oracle, and Microsoft
To download this report, which has been made available at no cost until the end of February, go to https://amalgaminsights.com/product/analyst-insight-cloud-foundry-and-kubernetes-different-paths-to-microservices
Research Fellow Tom Petrocelli recently recorded an on-demand BrightTALK webinar on Infrastructure as Code (IaC): a key trend for any company seeking to manage infrastructure at scale.
Petrocelli has previously covered this topic in additional research including
- Managing IT Complexity through Infrastructure as Code
- Infrastructure as Code Provides Advantages for Proactive Compliance and
- Petrocelli’s comprehensive Market Guide of key IaC trends and vendors
This webinar is a short introduction designed for IT professionals who are exploring Infrastructure as Code especially focusing on SysOps, managers (from mid-level to C-Suite), and system architects. As modern IT systems become more diverse and complex, managing them, especially at scale can become very difficult. Infrastructure as Code presents a new way of thinking about infrastructure management that alleviates many of these challenges.
This webinar discusses:
It’s not news that there is a lot of buzz around containers. As companies begin to widely deploy microservices architectures, containers are the obvious choice with which to implement them. As companies deploy container clusters into production, however, an issue has to be dealt with immediately: container architectures have a lot of moving parts. The…
API management is a necessary but boring practice. As developers make use of a mix of public cloud, purchased or open source libraries, and homegrown services, the number of APIs used by developers quickly renders pouring through documentation impractical.
Microservices, usually accessed via RESTFul APIs, cause API calls to rapidly proliferate. Even modest-sized microservices-based systems experience API overload quickly. Agile development can exacerbate the problem of understanding and using APIs. The rapid pace of Agile, especially Scrum, leaves little time for proper documentation of APIs. Documentation often takes a back seat to continuous deployment.