From Platform to Ecosystem |
|
ix | |
Preface |
|
xi | |
|
1 Revisiting Enterprise Development |
|
|
1 | (10) |
|
From Public to Private. Why Clouds? |
|
|
2 | (1) |
|
What "Cloud Native" Means |
|
|
3 | (1) |
|
Kubernetes-Native Development |
|
|
4 | (1) |
|
Containers and Orchestration for Developers |
|
|
4 | (1) |
|
|
4 | (1) |
|
|
5 | (1) |
|
Managing Development Complexity |
|
|
5 | (3) |
|
|
8 | (1) |
|
|
9 | (2) |
|
2 The Path to Cloud Native Java |
|
|
11 | (34) |
|
|
11 | (1) |
|
|
12 | (1) |
|
Create an Inventory Microservice with Quarkus |
|
|
13 | (1) |
|
Create Quarkus Maven Project |
|
|
14 | (3) |
|
|
17 | (2) |
|
|
19 | (1) |
|
|
20 | (3) |
|
Create a Catalog Microservice with Spring Boot |
|
|
23 | (1) |
|
|
23 | (3) |
|
|
26 | (2) |
|
|
28 | (1) |
|
|
29 | (4) |
|
Create a Gateway Service with Vert.x |
|
|
33 | (1) |
|
Create a Vert.x Maven Project |
|
|
34 | (2) |
|
|
36 | (5) |
|
Create a Frontend with Node.js and AngularJS |
|
|
41 | (1) |
|
|
42 | (2) |
|
|
44 | (1) |
|
3 Travel Light on Your Pathway |
|
|
45 | (16) |
|
Three-Tier or Distributed System |
|
|
45 | (1) |
|
Technology Updates, Modernization, and Transformation |
|
|
46 | (1) |
|
|
47 | (3) |
|
|
50 | (1) |
|
Kubernetes as the New Application Server? |
|
|
50 | (4) |
|
Define Your Target Platform |
|
|
54 | (2) |
|
Mandatory Migration Steps and Tools |
|
|
56 | (1) |
|
Create an Application Portfolio |
|
|
57 | (1) |
|
|
57 | (2) |
|
|
59 | (2) |
|
4 A Kubernetes-Based Software Development Platform |
|
|
61 | (24) |
|
Developers and Kubernetes |
|
|
61 | (1) |
|
|
62 | (1) |
|
What Kubernetes Doesn't Do |
|
|
63 | (1) |
|
|
63 | (1) |
|
|
64 | (1) |
|
|
65 | (1) |
|
Building Container Images |
|
|
66 | (1) |
|
|
67 | (1) |
|
|
68 | (1) |
|
|
69 | (1) |
|
|
69 | (2) |
|
|
71 | (2) |
|
|
73 | (3) |
|
|
76 | (1) |
|
|
76 | (2) |
|
|
78 | (5) |
|
|
83 | (2) |
|
5 Beyond Lift and Shift: Working with Legacy |
|
|
85 | (16) |
|
|
86 | (1) |
|
Assessing Applications for Migration |
|
|
86 | (5) |
|
Assessing Functionality for Migration |
|
|
91 | (1) |
|
|
92 | (1) |
|
Protecting Legacy (Replatform) |
|
|
92 | (3) |
|
Build Something New (Refactor) |
|
|
95 | (3) |
|
|
98 | (1) |
|
|
98 | (1) |
|
Long-Running Transactions |
|
|
99 | (1) |
|
Removing Old Code Too Quickly |
|
|
99 | (1) |
|
|
99 | (1) |
|
|
100 | (1) |
|
6 Building Kubernetes-Native Applications |
|
|
101 | (16) |
|
Find the Right Balance Between Scalability and Complexity |
|
|
101 | (1) |
|
Functional Requirements for Modern Architectures |
|
|
102 | (1) |
|
|
103 | (1) |
|
|
104 | (1) |
|
Security and Authorization |
|
|
104 | (1) |
|
|
105 | (1) |
|
|
106 | (1) |
|
|
106 | (1) |
|
|
107 | (3) |
|
|
110 | (1) |
|
|
111 | (1) |
|
Quarkus Remote Development Mode |
|
|
112 | (1) |
|
|
113 | (2) |
|
|
115 | (2) |
|
7 Tomorrow's Solutions: Serverless |
|
|
117 | (22) |
|
|
117 | (1) |
|
|
118 | (1) |
|
Use Cases: Data, AI, and Machine Learning |
|
|
119 | (1) |
|
Use Cases: Edge Computing and IoT |
|
|
120 | (1) |
|
Knative: Serverless for Kubernetes |
|
|
121 | (2) |
|
Event-Driven Serverless Architectures |
|
|
123 | (3) |
|
Function as a Service for Java Applications |
|
|
126 | (1) |
|
Functions Deployment for Java Applications |
|
|
127 | (1) |
|
Boson Function CLI (func) |
|
|
127 | (9) |
|
|
136 | (3) |
Index |
|
139 | |