Owner: Architect:

David Peraza

Story (Required)

As a Service Binding Developer, I would like to have the architecture diagram of a Service Oriented Architecture application and a mocked front-end for the final application, so that I can better show case our Service Binding technology.

Background (Required)

We have always being using PetClinic to demonstrate how service binding works with single deployment applications. This application is simple and it is very useful when testing simple uscases. However, to be able to see the benefits of Service Binding, it will make more sense to show how easy it is to bind an application composed of multiple micro-services (K8 Deployments and Services) and each of those depending on one or many Cloud Services (Database, Monitoring, MemCache)

We'd like to implement an e-commerce website with two exposed micro-services, one that manages Orders, the other manages the Catalog. When the user places a new order, the Catalog must be updated.

The communication between Orders and Catalog microservices should happen via a Message Broker (like Amazon SNS).

Glossary

NA

Out of scope

Backend applications.

This is not a product, just a demo app.

In Scope

Design of the SOA Application and development of a mocked front-end

Approach(Required)

Pick modern technology for Both, Frontend and Backend. Language selection is open but try to stay with the languages we use in our projects so that the demo app can be maintained (Golang, Python, JavaScript). Make it a simple Kubernetes application that shows how the services are being used

Demo requirements(Required)

A great demo will show the architecture explaining the design and then show up the front-end application.

Dependencies

NA

Edge Case

NA

Acceptance Criteria

The architecture and front-end application source code must be versioned on our demo repo
Drawio file and image for the designed architecture
README file with instructions to build and run the mocked application locally

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

v

Legend

Unknown

Verified

Unsatisfied