You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Develop and deploy an example microservices application**
3
+
**Develop and deploy an example microservices application within OpenShift**
4
4
5
-
Develop an example application with a three-tier microservices architecture and deploy it in IBM Cloud Kubernetes Service or Red Hat OpenShift on IBM Cloud using the IBM Garage Cloud-Native Toolkit Developer Environment including its Code Patterns.
5
+
Develop an example application with a three-tier microservices architecture and deploy it into a Red Hat OpenShift on AWS, Azure or IBM Cloud. This OpenShift development environment has be pre-configured with a sample [SDLC](https://cio-wiki.org/wiki/Software_Development_Life_Cycle_(SDLC))(Software Delivery Life Cycle) using the [Cloud-Native Toolkit](https://develop.cloudnativetoolkit.dev/).
6
6
7
7
## Business Need
8
8
@@ -20,31 +20,33 @@ An [MVP](https://www.ibm.com/garage/method/practices/think/practice_minimum_viab
20
20
21
21
## Architecture
22
22
23
-
We will build the Micro App using a three-tier microservices architecture. Each tier encapsulates a clean separation of concerns. Each app component will be modelled using _microservices_ and use a number of [polyglot](https://searchsoftwarequality.techtarget.com/definition/polyglot-programming) programming languages and frameworks. Data will be stored in IBM Cloudant and the Micro App will be secured using IBM App ID.
23
+
We will build an application that is made up of microservices in three-tier architecture. Each tier encapsulates a clean separation of concerns. Each app microservice component will be modelled using _microservices_ and use a number of [polyglot](https://searchsoftwarequality.techtarget.com/definition/polyglot-programming) programming languages and frameworks. Data will be stored in a NoSQL Database.
24
24
25
25
26
26
27
27
### User interface
28
28
29
-
The Micro App's user interface will look like this [wireframe](https://www.ibm.com/garage/method/practices/think/practice_wireframes/):
29
+
The user experience for the application has been designed by the design team and this drives the requirements for the development team this is a representation of the final user experience[wireframe](https://www.ibm.com/garage/method/practices/think/practice_wireframes/):
30
30
31
31
32
32
33
33
### Technical Requirements
34
34
35
-
The Micro App should adhere to the following technical requirements:
35
+
The Micro services should adhere to the following technical requirements:
36
36
37
37
- Microservices
38
38
- Stateless
39
39
- REST APIs
40
40
- Polyglot
41
-
- DevOps with CI/CD (continuous integration and continuous delivery)
41
+
- DevOps with CI/CD (continuous integration and continuous delivery)
42
+
- Use in cluster CI technology to be efficient and secure
43
+
- Use latest GitOps best practices
42
44
- Monitoring and logging
43
45
- Code analysis
44
46
- App security
45
-
- Deployed to Red Hat OpenShift on IBM Cloud or IBM Cloud Kubernetes Service
47
+
- Deployed to Red Hat OpenShift cluster which is based on Kubernetes open source technology
46
48
- Follow the [Carbon Design System](https://www.carbondesignsystem.com/) user experience
47
49
48
50
## Guide
49
51
50
-
You will approach creating the Micro App bottom up, meaning you will start by creating the backend microservice that manages integration with the data persistence and then build out the digital channel using a backend for frontend pattern. Finally, you will add a web UI to the solution.
52
+
You will approach creating the microservices bottom up, meaning you will start by creating the backend microservice that manages integration with the data persistence and then build out the digital channel using a backend for frontend pattern. Finally, you will add a web UI to the solution.
If you want to skip the guide and just get the components running, see [Deploy the Inventory App solution](#deploy-the-inventory-app-solution).
6
5
6
+
!!! Info
7
+
If you want to skip the step by step guide to how you build out each microservice you can go strait to the completed solution and get it running, see [Deploy the Inventory App solution](#deploy-the-inventory-app-solution). I would advise coming back and working through the steps, you will learn more about how these types of solutions are created and delivered.
7
8
8
9
## Deploy the Inventory App solution
9
10
10
-
If you were unable to get everything working, you can deploy the Inventory App solution.
11
-
11
+
In some cases with self pace hands on labs you may not get everything working. Cloud-Native development is a sort of skill and takes time to hone the craft. If you were unable to get everything working, you can deploy the Inventory App solution using the steps detailed below.
12
12
13
13
### Inventory Service
14
14
15
15
- Create a new project from the [Inventory Management Service solution template](https://github.com/ibm-ecosystem-lab/inventory-management-svc-intermediate/generate)
16
-
named `inventory-management-svc-solution`
16
+
named `inv-man-svc-sol-{initials}`
17
17
18
18
- Clone the repository to your local machine
19
19
@@ -26,7 +26,7 @@ named `inventory-management-svc-solution`
26
26
- Register the pipeline [register the pipeline](/developer-intermediate/deploy-app#5.-register-the-application-in-a-devops-pipeline)
27
27
28
28
```
29
-
oc pipeline --tekton
29
+
oc pipeline <git repo url> --tekton
30
30
```
31
31
32
32
replacing `{your initials}` with your actual initials
0 commit comments