That seems reasonable to me, Ken.
(In hindsight, I might say “…coherent grouping of business or mission functionality” (for purists in some domains who (sometimes legitimately) don’t consider their work to be
“business”, per se).
From: soa-rm@lists.oasis-open.org [mailto:soa-rm@lists.oasis-open.org]
On Behalf Of Ken Laskey
Sent: Friday, October 28, 2016 7:47 AM
To: Natale, Bob <RNATALE@mitre.org>
Cc: soa-rm@lists.oasis-open.org
Subject: Re: [soa-rm] compact blurbs on microservices
So would this generalize to
“An application is a composition of one or more
software components that when implemented together provides a coherent grouping of business functionality. What
has been popular over time as a software component has varied: Web Services were of interest during the emphasis on SOA; microservices currently receive the majority of attention.”
To you original query: “My biggest problem is I have yet to see a good definition of “application”. Is it just the user interface that calls microservices under the hood?” …
Taking the perspective of a microservices architecture evangelist, I’d answer “An application is a composition of one or more microservices and other implementation mechanisms
that provides a coherent grouping of business functionality.”
That’s quick n’ dirty but conveys the sense as I understand (in the microservices context).
and while the focus is really on OSGi, its discussion of microservices includes the following:
The first model is the microservices
model. With this model, components are defined as independent microservices that any application can use. They also have stateless behavior so they
can be replaced and scaled as needed. Additionally, they are independent of each other and of applications that use them, so deployment/redeployment of a microservice doesn't affect applications it serves.
But microservices might
be the biggest revolution in componentization. A microservice is a logic component deployed in RESTful form, designed to be accessed through a URL. Microservices easily address issues of component dependencies and avalanches of redeployments due to small component
changes because microservices are independent as long as the API call formats are maintained. Microservices won't change the modularity of JVM or provide an efficient way of managing remote-versus-local components, but they could significantly reduce the burden
of component management for distributed components.
My biggest problem is I have yet to see a good definition of “application”. Is it just the user interface that calls microservices under the hood?
Any favorite (attributable) definitions of application?
------------------------------------------------------------------------------
Dr. Kenneth Laskey
MITRE Corporation, M/S F510 phone: 703-983-7934
7515 Colshire Drive fax: 703-983-1379
McLean VA 22102-7508
|