Welcome!

Microservices Expo Authors: Liz McMillan, Pat Romanski, Carmen Gonzalez, Elizabeth White, Jason Bloomberg

Related Topics: Microservices Expo, @CloudExpo

Microservices Expo: Blog Feed Post

Microservices: New SOA or Buzzword? | @CloudExpo [#Microservices #API]

Microservices is a new architectural style based upon independent services

Capability Analysis
Source: English Wikipedia

Microservices is a new architectural style based upon independent services.

The terms Microservices and Microservices Architecture are often used. It is an architecture based on independent relatively small components named Micro Services.

Some people may think that Microservices Architecture is a new and improved Service Oriented Architecture (SOA). It is not.

Martin Fowler is the first name mentioned in articles about Micro Services. Fowler is a British Software Engineer specialized in Software development.

I read the article: Microservices in Fowler's Web site. I am more confused about Microservices characteristics after reading the article.

The article was written by James Lewis and Martin Fowler.

What Microservice Architecture is and what Microservice is?
The articles discussed the following characteristics of Microservice Architecture and Microservices:

1. It is a new Architectural style

OK, let's understand what is new and what is its Value Proposition.

2. "approach to developing a single application as a suite of small services"

Nothing to write home about. Remember Cool:Gen?

A leading Client/Server IDE. It was a leading Component Based Development (CBD) tool. Its first version was launch in 1987. It is easy to find other IDE tools which were available 15 years or twenty years ago and were based on CBD methodology.

The Services granularity is small, unlike the coarse grained granularity of SOA Services.

3. "each running in its own process and communicating with light weight mechanism, often an HTTP resource API."

This is a performance issue: is the Overhead of many Microservices small enough?

I am sure that for large applications it is not, unless light weight communication mechanism is used.

Similarly, REST is preferred over SOAP because of better Performance and reduced Complexity.

4. The Microservices are "independently deployable by fully automated deployment machinery"

It could be a good technical approach for Deployment and for Change Management.

5. Monolithic applications run a in a single process they are scaled by multiple instances. Each Microservice is deployed under a different process. No need to multiple instances, so Change Management is simpler and less error prawn.

Monolithic Applications are not Silo Systems or Monolithic Applications in SOA context. In this article they refer to Server Side only applications, while in SOA context they include all layers: Server as well as Clients and Middleware.

As in previous section the focus is technical. By running each Micro Process under different process, Performance could be improved and Deployment and Change Management of each Micro Service is less dependent on other Micro Services.

6. "These services are build around Business Capabilities"
Now I am really confused. How componentization of Application could be related to Business Capabilities?

Capabilities and SOA Services
Capabilities are defined as Coarse grained Business elements. Capability Analysis is used for bridging between Business Architecture and Service Oriented Architecture.

Capabilities are Business entities defining what and not How the Organization could do something Valuable.

System Analysis in Service Oriented Architecture could use Capability Analysis. After defining the Capabilities, you could map each Capability to Services i.e. according to the frequently used definition of Capabilities, a Capability is more Coarse Grained than a Service.

How could a Capacity will be related to a Fine Grained entity such as Microservice?

What is the relationship between an Inter-Application entity (Micro Service) and a Business Entity (Capability)?

I do not have adequate answers to those questions.

Even if you define Capability as a smaller Business entity mapped  Many to One to SOA Service, i.e. few capabilities included in a Service, I am still confused about its relationship to Micro Services.

It should be noted, that some companies, defined Capability as a less Coarse Grained entity than a SOA Service.

The Bottom Line
Microservice Architecture is a new architectural style using terminology and approach resembling Service Oriented Architecture. However, the scope of Micro Service Architecture is Inter-Application.

SOA scope is Enterprise and Virtual Enterprise. Virtual Enterprise may refer to Public Clouds and Hybrid Clouds, as well as other types of implementing some of the Applications or some of the Services outside the Enterprise boundaries.

SOA Services are defined by Business Services  boundaries. The alignment of Micro Services to Business Services is not well defined.

My Take
Microservice Architecture could be useful. It is a small scale SOA like Architecture within an Application. It should be compared to other approaches to defining and managing Application Components.

Service Oriented Architecture is defined in another level and is orthogonal to Inter-Application Architectural styles such as: Microservices Architecture or OMG's CBD model.

Micro Service Architecture could be useful for Agile Software Development Methodologies. It completes the methodology by adding a development and deployment style.  

More Stories By Avi Rosenthal

Ari has over 30 years of experience in IT across a wide variety of technology platforms, including application development, technology selection, application and infrastructure strategies, system design, middleware and transaction management technologies and security.

Positions held include CTO for one of the largest software houses in Israel as well as the CTO position for one of the largest ministries of the Israeli government.

Microservices Articles
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
"NetApp's vision is how we help organizations manage data - delivering the right data in the right place, in the right time, to the people who need it, and doing it agnostic to what the platform is," explained Josh Atwell, Developer Advocate for NetApp, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
The Jevons Paradox suggests that when technological advances increase efficiency of a resource, it results in an overall increase in consumption. Writing on the increased use of coal as a result of technological improvements, 19th-century economist William Stanley Jevons found that these improvements led to the development of new ways to utilize coal. In his session at 19th Cloud Expo, Mark Thiele, Chief Strategy Officer for Apcera, compared the Jevons Paradox to modern-day enterprise IT, examin...
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, discussed how to use Kubernetes to set up a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace. H...
Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, will discuss why containers should be paired with new architectural practices such as microservices ra...
In his session at 20th Cloud Expo, Scott Davis, CTO of Embotics, discussed how automation can provide the dynamic management required to cost-effectively deliver microservices and container solutions at scale. He also discussed how flexible automation is the key to effectively bridging and seamlessly coordinating both IT and developer needs for component orchestration across disparate clouds – an increasingly important requirement at today’s multi-cloud enterprise.
The Software Defined Data Center (SDDC), which enables organizations to seamlessly run in a hybrid cloud model (public + private cloud), is here to stay. IDC estimates that the software-defined networking market will be valued at $3.7 billion by 2016. Security is a key component and benefit of the SDDC, and offers an opportunity to build security 'from the ground up' and weave it into the environment from day one. In his session at 16th Cloud Expo, Reuven Harrison, CTO and Co-Founder of Tufin, ...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
TCP (Transmission Control Protocol) is a common and reliable transmission protocol on the Internet. TCP was introduced in the 70s by Stanford University for US Defense to establish connectivity between distributed systems to maintain a backup of defense information. At the time, TCP was introduced to communicate amongst a selected set of devices for a smaller dataset over shorter distances. As the Internet evolved, however, the number of applications and users, and the types of data accessed and...