From Spring Boot 2.2 to Spring Boot 2.3 #jsugToshiaki Maki
?
Spring Boot 2.3 will include improvements to support for containers and Kubernetes, as well as updates for Spring Framework 5.3 including support for JDK 17 LTS and GraalVM native images. Other new features in Spring Boot 2.3 include enhancements to Spring Data and a target release date of April 2020. Spring Framework 5.3 will build upon features introduced in 5.x such as RSocket and coroutines.
The document discusses a meetup about integrating Concourse and Spinnaker. It covers why Spinnaker is useful for continuous delivery, specifically blue/green deployments, rollbacks, and automated canary analysis. It then discusses how Concourse and Spinnaker can be integrated using the Concourse Spinnaker resource to trigger Spinnaker pipelines from Concourse and vice versa. A demo is shown of building a Docker image, deploying it to Spinnaker, running tests with JMeter, and rolling back if tests fail.
Serverless with Spring Cloud Function, Knative and riff #SpringOneTour #s1tToshiaki Maki
?
This document summarizes a presentation about serverless computing using Spring Cloud Function, Knative, and riff. It discusses what serverless computing is, an overview of Spring Cloud Function for developing serverless applications, and how Knative and riff can be used as platforms to deploy serverless workloads on Kubernetes. Code examples are provided to demonstrate invoking functions via HTTP and messaging with Spring Cloud Function and deploying functions to Knative and riff.
Spring Boot Actuator 2.0 & Micrometer #jjug_ccc #ccc_a1Toshiaki Maki
?
Spring Boot Actuator 2.0 provides additional monitoring endpoints for Spring Boot applications running in production. Micrometer allows instrumenting Spring Boot applications without vendor lock-in by providing common metrics that can be exported to systems like Prometheus, Datadog, and Cloud Foundry Metrics. Key features include multi-dimensional metrics with tags instead of hierarchies, histograms for response time distributions, and client-side percentiles. Monitoring of Spring Boot applications can be done on Cloud Foundry by scraping the /actuator/prometheus endpoint across application instances behind a load balancer.
Spring Boot Actuator 2.0 has been refactored and now supports Micrometer for instrumentation and metrics collection. Micrometer allows instrumentation without vendor lock-in and supports many monitoring systems including Prometheus, Datadog, and Cloud Foundry Metrics. New features in Spring Boot Actuator 2.0 include support for Spring WebFlux, more secure configuration of endpoints, and histograms and percentiles for more detailed metrics. Micrometer provides a common API for instruments like timers, counters, and gauges and supports adding custom meters.
Open Service Broker APIとKubernetes Service Catalog #k8sjpToshiaki Maki
?
The document discusses the Open Service Broker API and Kubernetes Service Catalog. It describes how the Service Broker API allows developers to provision and bind to services outside of Kubernetes. It then explains how the Kubernetes Service Catalog implements the Service Broker API to provide services within Kubernetes using new resource types like ServiceInstance and ServiceBinding. The document provides examples of installing brokers, listing available services, and creating instances and bindings.
Spring Cloud Function & Project riff #jsugToshiaki Maki
?
This document discusses Spring Cloud Function and Project Riff. It provides an overview of serverless computing and functions-as-a-service (FaaS). It introduces Spring Cloud Function as a way to write functions in Spring Boot and deploy them to various FaaS providers. It also describes Project Riff, an open source FaaS platform that runs on Kubernetes and provides event-driven functions through containers and sidecars that connect functions to event brokers. It demonstrates packaging functions as containers and connecting them to brokers through sidecars to handle event streaming and scaling of functions.
Introduction to Spring WebFlux #jsug #sf_a1Toshiaki Maki
?
The document provides an introduction and overview of Spring WebFlux, a non-blocking web framework for Spring. It discusses the differences between blocking and non-blocking web stacks, and how Spring WebFlux uses reactive streams and programming. Code examples are provided showing how to build reactive controllers and streams in Spring WebFlux that support backpressure.
BOSH / CF Deployment in modern ways #cf_tokyoToshiaki Maki
?
1. The document discusses deploying BOSH and Cloud Foundry using the BOSH CLI v2. It covers the general BOSH deployment workflow, differences between BOSH CLI v1 and v2, maintaining manifest files using operation files, downloading BOSH releases, variable interpolation, and provisioning the BOSH director.
2. It also provides examples of deploying Concourse on a single VM without a BOSH director using the BOSH CLI create-env command and different infrastructure configurations.
Why PCF is the best platform for Spring BootToshiaki Maki
?
Pivotal Cloud Foundry (PCF) provides many out-of-the-box features for managing and operating Spring Boot apps, including a cloud profile, Spring Cloud Connectors, Spring Cloud Services, a Trace Exporter, Spring Actuator support in Apps Manager, and a Metrics Forwarder Service. These features simplify development and operations of microservices built with Spring technologies when deployed to PCF.
This document provides instructions for installing and configuring Zipkin, an open source distributed tracing system. It describes how to download Zipkin, configure it to store traces in MySQL or Elasticsearch, and receive traces from Kafka. It also covers enabling OAuth2 authentication and securing the Zipkin UI and API endpoints.
The document discusses various boilerplate patterns related to building microservices using the Spring Framework and Spring Cloud. It outlines patterns for application coordination, configuration, operations for the JVM, runtime platform provisioning, and microservice operations. It also introduces Spring Cloud projects like Config Server, Eureka, Ribbon, Hystrix, Stream, and Sleuth that can help implement these patterns to build cloud-native microservice architectures.
Spring Framework 5.0による Reactive Web Application #JavaDayTokyoToshiaki Maki
?
The document discusses reactive programming and the Spring Framework 5.0 release. It provides an overview of reactive programming concepts like asynchronous non-blocking applications. It also discusses Reactive Streams and libraries like Reactor. Finally, it covers new features in Spring Framework 5.0 like performance improvements, support for JDK 9, and the introduction of reactive APIs in Spring.
The document discusses various topics related to Spring Boot including Spring Data REST, CSRF protection, and Cloud Foundry integration. It provides code examples for exposing repositories as REST APIs with Spring Data REST, handling errors and exceptions, and securing applications with CSRF tokens. It also briefly mentions Spring Boot features like configuration properties and the Actuator.
The document discusses Kotlin support in Spring Framework 5. It covers how Kotlin can be used with Spring Boot and Spring's programming model through features like extension functions and reified type parameters. It provides code examples of using Kotlin idioms with Spring components like the application context, JdbcTemplate, and RestTemplate to make the code more concise and readable. It also briefly mentions new features in Spring Framework 5 like reactive support using Spring WebFlux and using router functions with Kotlin.
Event Driven Microservices with Spring Cloud Stream #jjug_ccc #ccc_ab3Toshiaki Maki
?
The document describes Spring Cloud Stream, an event-driven microservice framework built on Spring Boot and Spring Integration. It provides primitives for building message-driven microservices including persistent publish-subscribe messaging, consumer groups, and support for multiple message brokers like RabbitMQ and Kafka. Applications are developed as message sources, sinks and processors. Spring Cloud Stream handles mapping of applications to messaging infrastructure.
Managing your Docker image continuously with Concourse CIToshiaki Maki
?
This document discusses managing Docker images continuously using Concourse CI. It describes using a Docker image resource in a Concourse pipeline configuration file to build a custom Docker image. The pipeline pulls from a Git repository, builds the image using a Dockerfile, and pushes the new image to a registry on each run, ensuring the image is always up to date.
Data Microservices with Spring Cloud Stream, Task, and Data Flow #jsug #spri...Toshiaki Maki
?
The document discusses Spring Cloud Data Flow, which provides a framework for building data pipelines using microservices. It describes how Spring Cloud Data Flow orchestrates long-lived streaming applications using Spring Cloud Stream and short-lived batch processing applications using Spring Cloud Task. It also discusses how these applications can be deployed on modern platforms using deployment-specific Spring Cloud Deployers.
Short Lived Tasks in Cloud Foundry #cfdtokyoToshiaki Maki
?
The document discusses different types of tasks in Cloud Foundry including long-running process (LRP) tasks, app process staging tasks, and app tasks. It provides examples of using the cf v3-run-task command to run tasks such as database migrations, flyway migrations, and a custom task to output a greeting.
IoT Devices Compliant with JC-STAR Using Linux as a Container OSTomohiro Saneyoshi
?
Security requirements for IoT devices are becoming more defined, as seen with the EU Cyber Resilience Act and Japan¨s JC-STAR.
It's common for IoT devices to run Linux as their operating system. However, adopting general-purpose Linux distributions like Ubuntu or Debian, or Yocto-based Linux, presents certain difficulties. This article outlines those difficulties.
It also, it highlights the security benefits of using a Linux-based container OS and explains how to adopt it with JC-STAR, using the "Armadillo Base OS" as an example.
Feb.25.2025@JAWS-UG IoT
40. いつも宥り軟
$ mvn spring-boot:run
´ (待)
2014-12-13 12:07:47.833 INFO --- [mple.App.main()]
s.b.c.e.t.TomcatEmbeddedServletContainer : Tomcat started
on port(s): 8443/https
2014-12-13 12:07:47.836 INFO --- [mple.App.main()]
com.example.App : Started App in
5.322 seconds (JVM running for 10.02)
41. いつも宥り軟
$ mvn spring-boot:run
´ (待)
2014-12-13 12:07:47.833 INFO --- [mple.App.main()]
s.b.c.e.t.TomcatEmbeddedServletContainer : Tomcat started
on port(s): 8443/https
2014-12-13 12:07:47.836 INFO --- [mple.App.main()]
com.example.App : Started App in
5.322 seconds (JVM running for 10.02)