Download to read offline
Uploaded byVMware Tanzu
SpringOne Tour: 10 Practical Tips for Building Native and Serverless Spring Applications
Serverless technology allows developers to deploy and execute code fragments in response to events without managing underlying infrastructure. This improves resource management and responsiveness. Spring Native further enhances the developer experience by allowing applications to deploy and run more quickly using a "closed world scenario" with static classpaths and bean definitions. While serverless is not truly without servers, it ease development and deployment by automating scaling. There are many serverless options available, but applications must be designed to complete tasks within one minute to be suitable. Evaluating use cases and migrating legacy code may take time to fully utilize serverless.
More Related Content
Similar to SpringOne Tour: 10 Practical Tips for Building Native and Serverless Spring Applications
SpringOne Tour: 10 Practical Tips for Building Native and Serverless Spring Applications
- 1. Tips on Serverless,Spring Native
- 2. grayma@vmware.com ~ ❯❯❯$ cat /var/diet/ops/description Good Day! Today I will talk about serverless tech. Why it’s important for resource management, and how native enhances the experience. We’ve probably all heard about ‘serverless’ and Are probably using it today. Even Mainframes have had features of serverless - think Time-Delayed-Queue jobs. But what is it to the developer? Introduction @mariogray Developer Advocate / Principal Technologist 2
- 3. Serverless 3 Key Criteria ● FaaSallows developers to deploy and execute fragments of code ( functions ) in response to events, without managing the underlying infrastructure ● EDA enables function triggers, enabling responsive, scalable and decoupled apps. ● Management: DBMS, MQ’s, API’s that are consumable by developers, benefited by infra management.
- 4.
- 5. Old School 5 Epic LoadTimes …
- 6. Faster, please 6 Native tothe rescue!
- 7. Static World 7 Native isa ‘Closed World Scenario’ ● Fixed Classpath at build-time ● Static Bean definitions at runtime so don’t… ○ @Profile ○ @ConditionalOnProperty (enable) ● You may interact with AOT engine to generate *hints* that tell it what classes should be seen (even if they’re not apparent during build-time)
- 8. Deploy please? 8 Begin ServerlessDeployment
- 9. Moving on.. 9 Conclusions ● Serverlessis not *REALLY* serverless. The developer just doesn’t think about them. ● Eases development, deployment, scaling. ● There are a plethora of options to choose: Knative, AWS lambda, Google Fn, Azure Fn, and more! ● Time sensitive: Jobs must complete in under 1 minute. ● May take time to evaluate use case if existing legacy code is to be migrated.
- 10.
Editor's Notes
- #3 exec(‘/bin/rewrite’) > /dev/profile 2>/dev/null;
- #4 exec(‘/bin/rewrite’) > /dev/profile 2>/dev/null;
- #5 exec(‘/bin/rewrite’) > /dev/profile 2>/dev/null;
- #6 exec(‘/bin/rewrite’) > /dev/profile 2>/dev/null;
- #7 exec(‘/bin/rewrite’) > /dev/profile 2>/dev/null;
- #8 exec(‘/bin/rewrite’) > /dev/profile 2>/dev/null;
- #9 exec(‘/bin/rewrite’) > /dev/profile 2>/dev/null;
- #10 Because SCS has built in support for Spring Cloud Function, java.util.function.* beans translate to EDA idioms
- #11 Reactive Data, Web then CDC