forked from spring-projects/spring-petclinic
-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathscript.txt
133 lines (106 loc) · 4.91 KB
/
script.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
Introduction to Visual Studio Code
Spring Boot Extension Pack
- Extensions included in the pack
Inner Loop Demo
- Getting Started
- Spring Initializr integration
- Use Spring Petclinic from Getting Started guide
- Spring Tooling
- Run the application and access it through the code lenses
- Refresh Live Process connection to update IDE with metrics
- Code navigation, project symbols
- Show live Hovers
- Debugging
- Show debugging flow and hot code replace
- Spring Boot Dashboard
- Show beans, mappings, memory views
- Talk about Spring Boot auto-configuration insights
- Testing
- JUnit Test runner to execute tests without leaving the IDE
- (Optional) Talk about Spring validations - best practices while coding
- Summarize the end-to-end Spring development experience
Outer Loop Demo
- MONITOR
- OPEN "Application Live View"
- OPEN "View Live Information"
- OPEN OwnerController.java
- REFRESH ">Spring boot: manage live spring boot process connections"
- DEMO
- Beans
- Endpoint mapping
- DEBUG
- MIGRATE
- MIGRATE ">Spring boot: upgrade spring boot version"
- EXPLAIN openrewrite recipes from Spring Boot language server (3 levels down)
- (Optional) Show validations for best practices using openrewrite
- COMMIT
- DEPLOY
- BUILD
- Microsoft openjdk
- CONTAINER
- explain buildpacks
- ROLL-OUT
-Q&A
Talking Points:
Introduction:
Setting the Stage:
• Highlight the exciting features and capabilities for building Java and Spring Boot applications in Visual Studio Code (VS Code).
• Emphasize that the focus will be on live demonstrations to showcase the tools in action.
Why VS Code:
• Explain the advantages of using Visual Studio Code as an editor-centric environment that enhances code creation experience.
• Mention its lightweight nature, quick start-up times, and responsiveness, making it user-friendly.
• Note its evolution from a web development tool to support various languages through extensions.
Spring Tooling Extension Pack:
• Introduce the Visual Studio Code extension pack specifically tailored for Spring Boot development.
• Highlight the extensions included, such as Spring Initializer, Spring Tools, and Spring Boot Dashboard.
Demo Plan Overview:
• Outline the structure of the demo, focusing on the inner loop scenario.
• Mention that the goal is to showcase the power of tooling to develop, debug, and test applications.
Live Coding and Debugging:
• Walk the audience through the process of creating a Spring Boot project using Spring Initializer.
• Showcase how to start the application in debug mode within VS Code.
• Demonstrate the convenience of hot code replacement, which allows for seamless debugging without application restarts.
• Showcase the Spring Boot Dashboard's visualization of live information from the application.
Interaction with Rory:
• Experience with creating spring boot projects
• Engage Rory while showing the live metrics for APIs, memory view
JUnit Testing and Code Analysis:
• Explain how VS Code supports running JUnit test cases.
Code Analysis and Validation:
• Discuss code analysis and validation features that help ensure code quality and adherence to Spring coding standards.
• Summarize the inner-loop journey: streamlined project generation, efficient development, debugging, testing, and validations.
Transition to Rory:
• Transition to the next part of the presentation, where Rory will take over to discuss outer-loop scenarios.
Wrap-up:
• Thank the audience for their time and attention.
• Encourage attendees to check out the provided links for more information and resources.
Talking Points:
- Introduction
- DevOps Role and Responsibilities
- Tasks: Monitor, Migrate, and Deploy.
- Utilization of GitHub actions and buildpacks.io.
- Deployment strategy for Kubernetes clusters.
- Reflections on Past Experience
- Evolution from manual Spring projects to using start.spring.io.
- Tools and Technologies Discussion
- Debate and preference between Maven and Gradle.
- Technical Demonstrations
- The power and efficiency of hot code debugging.
- Exploration of Tansu dev tools in Kubernetes clusters for live views.
- Process and methods for telemetry addition.
- Live debugging capabilities on Kubernetes.
- Migration Process
- Live migration, contrasting with Udani's demonstration.
- Upgrades and Best Practices
- Upgrading to Spring Boot 3.1.2.
- Emphasis on configuration best practices.
- Patching approach for files.
- Deployment Strategy
- Committing changes and integrating with source control.
- Use of GitHub Copilot for CI/CD setup.
- Build and deployment process elucidation.
Appendix:
To create an Azure User for the action:
- `az ad sp create-for-rbac --name springone --role contributor --scopes /subscriptions/<your sub>/resourceGroups/springoneent --sdk-auth`
Extension
https://network.tanzu.vmware.com/products/tanzu-java-azure-buildpack