Re: [soa-rm] Wednesday topics (highlight REST)

The REST paradigm is about constructing the URL under certain rules. Period. It claims that ANY business operation can be finally expressed as get-data and set-data. I have a long discusstion with the REST community on this topic and whether REST is a service or a service interface. 

 

The outcomes are:

1) REST is the _interface_ to the service=working entity

2) yes, any business operation can be finally expressed as get-data and set-data but doing this is equal to using Lotus Script or Assembler - extremely inefficient and not performing.

 

A conclusion for myself: if I need to access data in applications or via HTTP, I use REST; if I need to access a capability or execute business commands more complex than get/set, I use another interface, which includes Web Service.

 

Regards,

- Michael

 

Sent: Wednesday, September 16, 2015 at 2:39 AM

From: "Ken Laskey" <>

To: 

Subject: [soa-rm] Wednesday topics (highlight REST)

I am behind in responding to some of our work in progress, partly because new challenges continue to arise.  Martin raised the question about microservices.  I have day job interest in using RESTful services, but the challenge is to understand what constitutes a beneficial use of the REST paradigm vs. just using a URL to tunnel through HTTP.

 

I raised some of these questions during an Amazon Web Services brief and the following is some material sent my way on these topics.

 

Here is an AWS article that discusses the concepts I was talking about using Lambda to run a micro service architecture instead of setting up servers to run your architecture.

 

SquirrelBin: A Serverless Microservice Using AWS Lambda

https://aws.amazon.com/blogs/compute/the-squirrelbin-architecture-a-serverless-microservice-using-aws-lambda/

--------------------

 

This is a discussion of how Netflix morphed from a private datacenter based monolithic application into a cloud based micro service architecture with high redundancy on AWS:

 

AWS re:Invent 2014 | (PFC304) Interprocess Comms in Cloud: Pros, Cons of Microservices Architectures

YouTube Video

SlideShare

--------------------

 

This reinvent video discusses another commercial organization making this change as well (Nike).

 

AWS re:Invent 2014 | (ARC308) Nike's Journey into Microservices

https://www.youtube.com/watch?v=h30ViSEZzW0

 

--------------------

 

Here is a presentation deck for an interesting discussion on the subject that was done at one of the AWS User groups last year.

Scaling micro-services Architecture on AWS (platform Lead at Hailo)

--------------------

 

Very good article discussing a move from a standard architecture to micro-services based development

http://www.infoq.com/articles/gilt-deploying-microservices-aws

--------------------

 

Another good articles discussing how to use containers to build micro services

https://medium.com/aws-activate-startup-blog/using-containers-to-build-a-microservices-architecture-6e1b8bacb7d1

 

--------------------

 

This discusses using AWS OPSWorks to create a micro service architecture in AWS

Managing Multi-Tiered Applications with AWS OpsWorks

 

--------------------

 

Here is an AWS whitepaper that discusses using Linux containers to deploy micro services using Docker.

Docker on AWS

 

 

I haven’t gone through nearly enough of this, so I encourage others to do a little reading and seeing where you find goodness.

 

Still interest in the SOA ontology and working on an update from William.

 

Dial-in information available on request.  That will be coming out tonight or tomorrow.

 

*** remember, meeting time is 11:30 AM - 1:00 PM ET ***

 

Talk with you tomorrow.

 

Ken

 

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