This article provides a detailed walkthrough of SpringBoot plugin development, covering the benefits of modular decoupling, common implementation approaches such as Java SPI, custom configuration, Spring factories, and practical code examples that demonstrate how to create, load, and use plugins for extensible SMS services.
This article explains how Spring Boot’s plugin mechanisms—such as Java SPI, custom configuration files, and Spring Factories—enable module decoupling, extensibility, and easy third‑party integration, and walks through complete code examples and a real‑world SMS‑sending case study.
This guide explains Java's Service Provider Interface (SPI) mechanism, compares it with APIs, and walks through creating a multi‑module Maven project that defines SPI interfaces, implements plugins, loads external JARs with a custom class loader, and integrates the plugins into a Spring Boot application for dynamic authentication.
This article introduces Java's Service Provider Interface (SPI) mechanism, explaining its role in decoupling interface definitions from implementations, with examples in JDBC, Spring Boot, and Dubbo.
This article explains Java's Service Provider Interface (SPI) mechanism and compares it with Dubbo's enhanced SPI implementation, highlighting how Dubbo addresses the limitations of native Java SPI through configuration format changes and lazy loading.
This article explains how to develop, package, and deploy custom Trino plugins—illustrated with an access‑control plugin—by using Java SPI, Maven dependencies, implementing the Plugin and SystemAccessControl interfaces, and configuring the plugin in Trino’s configuration files.
This article explains the principles and implementations of Java's built‑in SPI, Dubbo's enhanced SPI, and Spring's SPI mechanisms, compares their designs, walks through concrete code examples, and shows how they can be applied for dynamic extension in real projects.
The article introduces mica-auto, a Spring Cloud component that uses annotation processing to automatically generate starter configurations, SPI entries, and Feign client setups, and provides usage examples for Maven and Gradle along with recent updates.
The mica-auto component of the Mica Spring Cloud framework provides a set of tools that automatically generate essential Spring Boot starter files such as spring.factories, spring‑devtools.properties, and Java SPI configurations, simplifying multi‑module backend projects and supporting annotations like @AutoService for seamless integration.
This article explains the essence of scalability as a placeholder concept, outlines a four‑step method—standardize, identify, register, use—and demonstrates its application through Java SPI and a coupon platform case study to design extensible backend systems.
Java’s Service Provider Interface (SPI) is a built‑in discovery mechanism that decouples implementation from usage by letting providers place fully qualified class names in META‑INF/services files, enabling frameworks such as JDBC, logging, and Dubbo to load multiple vendor implementations at runtime via ServiceLoader, though it has limitations like lack of on‑demand loading and concurrency issues.
