OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [soa-rm] compact blurbs on microservices


Rex,

The Wikipedia article says:
an application is a computer program designed to help people perform an activity.

While I’d say that is correct, I’m not sure it’s useful.  BTW, the discussion on slicing and dicing what is application vs. operating system vs. utility … was entertaining.

What I am looking for is a definition of application in the context of “components are defined as independent microservices that any application can use”.  I don’t necessarily need an exhaustive taxonomy but this goes back to old discussions of when is an application offered as a service or when does a service constitute an application.

I’ll take anything that provides some clarity.

Ken


On Oct 27, 2016, at 2:32 PM, rexbroo <rexb@starbourne.com> wrote:

The conventional definition of application software from Wikipedia still works for me. https://en.wikipedia.org/wiki/Application_software

However, I think you may be looking for the definition of something in relation to the conventional definition of application that is like microservivce is to servivce, e.g. micro application, or containerized/componentized application. Correct?

Rex


On 10/27/2016 10:41 AM, Ken Laskey wrote:
Came across this article


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.

and

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?

Ken 


------------------------------------------------------------------------------
Dr. Kenneth Laskey
MITRE Corporation, M/S F510          phone: 703-983-7934
7515 Colshire Drive                           fax: 703-983-1379
McLean VA 22102-7508


-- 
Rex Brooks
Starbourne Communications Design
Email: rexb@starbourne.com
GeoAddress:
1361 Addison St. Apt. A
Berkeley, CA 94702
Phone: 510-898-0670 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]