dubbo nacos Spring Boot
. This article will not cover too much theoretical knowledge, but will write the simplest example to illustrate how dubbo can be integrated with nacos to quickly build a development environment.Article Directory
- ##Environment preparation
- dubbo introduction
- Nacos environment preparation
- Integration of Nacos and dubbo
- Project management specifications
- dubbo integration nacos case
- Create public interface module
- Create service provider module
- Create service consumer module
- Service call test
- Summary of this article
Environment preparation
Calling relationship between dubbo core nodes


Calling relationship description
The service container is responsible for starting, loading, and running the service provider. When the service provider starts, it registers the services it provides with the registration center. When the service consumer starts, he subscribes to the registration center for the services he needs. The registration center returns the service provider address list to the consumer. If there is a change, the registration center will push the change data to the consumer based on the long connection. The service consumer selects a provider to call from the provider address list based on the soft load balancing algorithm. If the call fails, it selects another provider to call. Service consumers and providers accumulate the number of calls and call times in memory, and regularly send statistical data to the monitoring center every minute.
Nacos environment preparation
Start nacos, this article uses nacos1 .4.3 version

Open nacos control panel

Integration of Nacos and dubbo
For the convenience of everyone’s understanding, here it is written Output the corresponding producer and consumer Demo codes, as well as the registration center used.

Project management specifications
Between springboot, netflix and cloud alibaba There is a corresponding relationship between versions. The version selected for this article is as follows

There is a corresponding relationship between dubbo and cloud alibaba. The version selected for this article is as follows

In order to facilitate subsequent development using SpringCloud Alibaba
, first create a parent project of pom type, which is mainly used for project technology stack version management, and create a maven project. The name is spring-cloud-alibaba-example
, remove the src file and modify the pom file
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>ah.wideth</groupId> <artifactId>spring-cloud-alibaba-example</artifactId> <version>1.0-SNAPSHOT</version> <parent> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-parent</artifactId> <version>2.3.12.RELEASE</version> <relativePath/> <!-- lookup parent from repository --> </parent> <packaging>pom</packaging> <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <java.version>1.8</java.version> <spring-cloud.version>Hoxton.SR12</spring-cloud.version> <com-alibaba-cloud.version>2.2.7.RELEASE</com-alibaba-cloud.version> </properties> <!--对项目版本进行管理--> <dependencyManagement> <dependencies> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-dependencies</artifactId> <version>${spring-cloud.version}</version> <type>pom</type> <scope>import</scope> </dependency> <dependency> <groupId>com.alibaba.cloud</groupId> <artifactId>spring-cloud-alibaba-dependencies</artifactId> <version>${com-alibaba-cloud.version}</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> </project>
All subsequent projects created will be placed in this directory. You only need to declare the groupId and artifactId, and it will automatically Reference the version of the parent project spring-cloud-alibaba-example
. Rather than saying it is a parent project, it is better to say it is a root project: because every time you learn a new technology, a real parent project will be created, and many sub-projects will be created under the corresponding parent project

dubbo integration nacos case
The case in this article is the above nacos development example Continuing to write on the basis of. Let's start creating our project and paste my directory structure.

Module Description
public-api
公共接口模块(接口),供服务消费者和服务提供者调用。dubbo-provider
服务提供者模块(接口实现类),引入了public-api
模块dubbo-consumer
服务消费者模块(controller
),引入了public-api
模块消费者和提供者通过公共接口模块进行rpc远程调用
父工程pom文件
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <parent> <artifactId>spring-cloud-alibaba-example</artifactId> <groupId>ah.wideth</groupId> <version>1.0-SNAPSHOT</version> </parent> <modules> <module>public-api</module> <module>dubbo-provider</module> <module>dubbo-consumer</module> </modules> <artifactId>dubbo-nacos-example</artifactId> <name>dubbo-nacos-example</name> <description>duboo与nacos整合的父工程</description> <packaging>pom</packaging> <properties> <java.version>1.8</java.version> <project.build.sourceEncoding>utf-8</project.build.sourceEncoding> <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding> <dubbo.version>2.7.13</dubbo.version> <nacos.version>1.4.1</nacos.version> </properties> <dependencies> <dependency> <groupId>com.alibaba.cloud</groupId> <artifactId>spring-cloud-starter-alibaba-nacos-discovery</artifactId> <!--解决nacos-client2.0报错的问题--> <exclusions> <exclusion> <artifactId>nacos-client</artifactId> <groupId>com.alibaba.nacos</groupId> </exclusion> </exclusions> </dependency> <!--dubbo相关--> <dependency> <groupId>org.apache.dubbo</groupId> <artifactId>dubbo-spring-boot-starter</artifactId> <version>${dubbo.version}</version> </dependency> <dependency> <groupId>org.apache.dubbo</groupId> <artifactId>dubbo-registry-nacos</artifactId> <version>${dubbo.version}</version> </dependency> <dependency> <groupId>com.alibaba.nacos</groupId> <artifactId>nacos-client</artifactId> <version>${nacos.version}</version> </dependency> <!-- 解决dubbo2.7.13jar包冲突问题--> <dependency> <groupId>com.alibaba.spring</groupId> <artifactId>spring-context-support</artifactId> <version>1.0.11</version> </dependency> <dependency> <groupId>org.apache.dubbo</groupId> <artifactId>dubbo</artifactId> <version>${dubbo.version}</version> <exclusions> <exclusion> <groupId>org.springframework</groupId> <artifactId>spring</artifactId> </exclusion> <exclusion> <groupId>javax.servlet</groupId> <artifactId>servlet-api</artifactId> </exclusion> <exclusion> <groupId>log4j</groupId> <artifactId>log4j</artifactId> </exclusion> </exclusions> </dependency> </dependencies> </project>

创建公共接口模块
pom文件
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <parent> <artifactId>dubbo-nacos-example</artifactId> <groupId>ah.wideth</groupId> <version>1.0-SNAPSHOT</version> </parent> <artifactId>public-api</artifactId> <name>public-api</name> <description>api公用接口</description> <packaging>jar</packaging> <properties> <java.version>1.8</java.version> <project.build.sourceEncoding>utf-8</project.build.sourceEncoding> <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding> </properties> <dependencies> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-web</artifactId> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> </plugin> </plugins> </build> </project>

公共接口模块里面只有一个接口,没有配置文件,打jar包
package ah.wideth.api; /** * 让生产者和服务消 * 费者来使用这个接口 */ public interface InfoService { String getInfo(); }

创建服务提供者模块
pom文件
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <parent> <artifactId>dubbo-nacos-example</artifactId> <groupId>ah.wideth</groupId> <version>1.0-SNAPSHOT</version> </parent> <artifactId>dubbo-provider</artifactId> <name>dubbo-provider</name> <description>dubbo的服务提供者模块</description> <properties> <java.version>1.8</java.version> <project.build.sourceEncoding>utf-8</project.build.sourceEncoding> <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding> </properties> <dependencies> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-web</artifactId> </dependency> <!--引入公共接口模块--> <dependency> <groupId>${project.groupId}</groupId> <artifactId>public-api</artifactId> <version>${project.version}</version> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> </plugin> </plugins> </build> </project>
application.yml配置文件
server: port: 8180 spring: application: name: dubbo-provider dubbo: registry: address: nacos://127.0.0.1:8848 #注册地址 application: name: dubbo-provider #应用名 protocol: name: dubbo #dubbo协议 port: 20880 #协议端口 scan: base-packages: ah.wideth.impl #扫包范围 provider: timeout: 30000 #超时时间
接口实现类,该类实现了上面我们在公共接口模块创建的接口
package ah.wideth.impl; import ah.wideth.api.InfoService; import org.apache.dubbo.config.annotation.DubboService; import org.springframework.stereotype.Component; // dubbo提供的Service注解,用于声明对外暴露服务 // Service引入的是org.apache.dubbo.config.annotation.Service包 @Component @DubboService public class InfoServiceImpl implements InfoService { @Override public String getInfo() { return "hello,这里是dubbo-provider模块!"; } }
服务提供者启动类
package ah.wideth; import org.apache.dubbo.config.spring.context.annotation.EnableDubbo; import org.springframework.boot.SpringApplication; import org.springframework.boot.autoconfigure.SpringBootApplication; import org.springframework.cloud.client.discovery.EnableDiscoveryClient; @EnableDubbo @EnableDiscoveryClient @SpringBootApplication public class DubboProviderApplication { public static void main(String[] args) { SpringApplication.run(DubboProviderApplication.class, args); System.out.println("dubbo服务提供者8180启动了"); } }
创建服务消费者模块
pom文件
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <parent> <artifactId>dubbo-nacos-example</artifactId> <groupId>ah.wideth</groupId> <version>1.0-SNAPSHOT</version> </parent> <artifactId>dubbo-consumer</artifactId> <name>dubbo-consumer</name> <description>dubbo的服务消费者模块</description> <properties> <java.version>1.8</java.version> <project.build.sourceEncoding>utf-8</project.build.sourceEncoding> <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding> </properties> <dependencies> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-web</artifactId> </dependency> <!--引入公共接口模块--> <dependency> <groupId>${project.groupId}</groupId> <artifactId>public-api</artifactId> <version>${project.version}</version> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> </plugin> </plugins> </build> </project>
application.yml配置文件
server: port: 8181 spring: application: name: dubbo-consumer dubbo: registry: address: nacos://127.0.0.1:8848 #注册地址 application: name: dubbo-consumer #应用名 consumer: timeout: 30000 #超时时间
controller,调用公共接口模块创建的接口
package ah.wideth.controller; import ah.wideth.api.InfoService; import org.apache.dubbo.config.annotation.DubboReference; import org.springframework.web.bind.annotation.GetMapping; import org.springframework.web.bind.annotation.RestController; @RestController public class InfoController { //dumbo提供的Reference注解,用于调用远程服务 @DubboReference(check = false) private InfoService infoService; @GetMapping("/getInfo") public String getInfo(){ return infoService.getInfo(); } }
服务消费者启动类
package ah.wideth; import org.apache.dubbo.config.spring.context.annotation.EnableDubbo; import org.springframework.boot.SpringApplication; import org.springframework.boot.autoconfigure.SpringBootApplication; import org.springframework.cloud.client.discovery.EnableDiscoveryClient; @EnableDubbo @EnableDiscoveryClient @SpringBootApplication public class DubboConsumerApplication { public static void main(String[] args) { SpringApplication.run(DubboConsumerApplication.class, args); System.out.println("dubbo服务消费者8181启动了"); } }
服务调用测试
打开Nacos控制面板查看注册中心中的服务

启动nacos,启动服务提供者和服务消费者,调用服务消费者的getInfo方法,服务提供者会返回结果
本文小结
本文编写了一个例子来对dubbo整合nacos进行服务调用的例子,不过要注意jar包的冲突问题。
The above is the detailed content of SpringBoot+Dubbo+Nacos development practical tutorial. For more information, please follow other related articles on the PHP Chinese website!

Bytecodeachievesplatformindependencebybeingexecutedbyavirtualmachine(VM),allowingcodetorunonanyplatformwiththeappropriateVM.Forexample,JavabytecodecanrunonanydevicewithaJVM,enabling"writeonce,runanywhere"functionality.Whilebytecodeoffersenh

Java cannot achieve 100% platform independence, but its platform independence is implemented through JVM and bytecode to ensure that the code runs on different platforms. Specific implementations include: 1. Compilation into bytecode; 2. Interpretation and execution of JVM; 3. Consistency of the standard library. However, JVM implementation differences, operating system and hardware differences, and compatibility of third-party libraries may affect its platform independence.

Java realizes platform independence through "write once, run everywhere" and improves code maintainability: 1. High code reuse and reduces duplicate development; 2. Low maintenance cost, only one modification is required; 3. High team collaboration efficiency is high, convenient for knowledge sharing.

The main challenges facing creating a JVM on a new platform include hardware compatibility, operating system compatibility, and performance optimization. 1. Hardware compatibility: It is necessary to ensure that the JVM can correctly use the processor instruction set of the new platform, such as RISC-V. 2. Operating system compatibility: The JVM needs to correctly call the system API of the new platform, such as Linux. 3. Performance optimization: Performance testing and tuning are required, and the garbage collection strategy is adjusted to adapt to the memory characteristics of the new platform.

JavaFXeffectivelyaddressesplatforminconsistenciesinGUIdevelopmentbyusingaplatform-agnosticscenegraphandCSSstyling.1)Itabstractsplatformspecificsthroughascenegraph,ensuringconsistentrenderingacrossWindows,macOS,andLinux.2)CSSstylingallowsforfine-tunin

JVM works by converting Java code into machine code and managing resources. 1) Class loading: Load the .class file into memory. 2) Runtime data area: manage memory area. 3) Execution engine: interpret or compile execution bytecode. 4) Local method interface: interact with the operating system through JNI.

JVM enables Java to run across platforms. 1) JVM loads, validates and executes bytecode. 2) JVM's work includes class loading, bytecode verification, interpretation execution and memory management. 3) JVM supports advanced features such as dynamic class loading and reflection.

Java applications can run on different operating systems through the following steps: 1) Use File or Paths class to process file paths; 2) Set and obtain environment variables through System.getenv(); 3) Use Maven or Gradle to manage dependencies and test. Java's cross-platform capabilities rely on the JVM's abstraction layer, but still require manual handling of certain operating system-specific features.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

Notepad++7.3.1
Easy-to-use and free code editor

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software
