The state-of-the-art Dashboard of Apache RoccketMQ provides excellent monitoring capability. Various graphs and statistics of events, performance and system information of clients and application is evidently made available to the user.

Related tags

rocketmq-dashboard
Overview

RocketMQ Dashboard Build Status Coverage Status

License Average time to resolve an issue Percentage of issues still open Twitter Follow

How To Install

With Docker

  • get docker image
mvn clean package -Dmaven.test.skip=true docker:build

or

docker pull apacherocketmq/rocketmq-console

currently the newest available docker image is apacherocketmq/rocketmq-console:2.0.0

  • run it (change namesvrAddr and port yourself)
docker run -e "JAVA_OPTS=-Drocketmq.namesrv.addr=127.0.0.1:9876 -Dcom.rocketmq.sendMessageWithVIPChannel=false" -p 8080:8080 -t apacherocketmq/rocketmq-console-ng

or

docker run -e "JAVA_OPTS=-Drocketmq.namesrv.addr=127.0.0.1:9876 -Dcom.rocketmq.sendMessageWithVIPChannel=false" -p 8080:8080 -t apacherocketmq/rocketmq-console-ng:2.0.0

Without Docker

require java 1.8+

mvn spring-boot:run

or

mvn clean package -Dmaven.test.skip=true
java -jar target/rocketmq-dashboard-2.0.0.jar

Tips

  • if you download package slow,you can change maven's mirror(maven's settings.xml)

    <mirrors>
        <mirror>
              <id>alimaven</id>
              <name>aliyun maven</name>
              <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
              <mirrorOf>central</mirrorOf>        
        </mirror>
    </mirrors>
    
  • if you use the rocketmq < 3.5.8,please add -Dcom.rocketmq.sendMessageWithVIPChannel=false when you start rocketmq-dashboard(or you can change it in ops page)

  • change the rocketmq.config.namesrvAddr in resource/application.properties.(or you can change it in ops page)

UserGuide

English

中文

Contributing

We are always very happy to have contributions, whether for trivial cleanups or big new features. Please see the RocketMQ main website to read details.

License

Apache License, Version 2.0 Copyright (C) Apache Software Foundation

Issues
  • [ISSUE #5]Add permission control when loginRequired is true.

    [ISSUE #5]Add permission control when loginRequired is true.

    What is the purpose of the change

    #5

    When the login user calls all interfaces, the permission of each interface is verified by AOP, by checking whether the role to which the user belongs has the access permission of the interface. All interface urls that a common user role has access permissions are saved in a file. The file is hot updated to facilitate adding or deleting permissions.

    Brief changelog

    XX

    Verifying this change

    XXXX

    Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

    • [x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
    • [x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
    • [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    • [x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
    • [x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.
    • [ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.
    opened by zhangjidi2016 10
  • manifest for docker.io/apacherocketmq/rocketmq-console:latest not found

    manifest for docker.io/apacherocketmq/rocketmq-console:latest not found

    docker pull apacherocketmq/rocketmq-console Using default tag: latest Trying to pull repository docker.io/apacherocketmq/rocketmq-console ... manifest for docker.io/apacherocketmq/rocketmq-console:latest not found

    daemon.json { "registry-mirrors": ["https://registry.docker-cn.com"] }

    Which mirror provides acessible image

    opened by fwhezfwhez 3
  • why this happened?

    why this happened?

    [2021-08-29 18:29:36.297] ERROR Application run failed java.lang.NoSuchMethodError: org.yaml.snakeyaml.nodes.ScalarNode.getScalarStyle()Lorg/yaml/snakeyaml/DumperOptions$ScalarStyle; at org.springframework.boot.env.OriginTrackedYamlLoader$KeyScalarNode.(OriginTrackedYamlLoader.java:124) at org.springframework.boot.env.OriginTrackedYamlLoader$KeyScalarNode.get(OriginTrackedYamlLoader.java:135) at org.springframework.boot.env.OriginTrackedYamlLoader$KeyScalarNode.get(OriginTrackedYamlLoader.java:130) at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195) at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655) at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484) at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474) at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913) at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578) at org.springframework.boot.env.OriginTrackedYamlLoader$OriginTrackingConstructor.replaceMappingNodeKeys(OriginTrackedYamlLoader.java:98) at org.springframework.boot.env.OriginTrackedYamlLoader$OriginTrackingConstructor.constructObject(OriginTrackedYamlLoader.java:92) at org.yaml.snakeyaml.constructor.BaseConstructor.constructDocument(BaseConstructor.java:161) at org.yaml.snakeyaml.constructor.BaseConstructor.getData(BaseConstructor.java:127) at org.yaml.snakeyaml.Yaml$1.next(Yaml.java:547)

    opened by 953761972 2
  • [ISSUE #16]Use an object pool to manage DefaultMQAdminExt objects.

    [ISSUE #16]Use an object pool to manage DefaultMQAdminExt objects.

    What is the purpose of the change

    #16

    Brief changelog

    XX

    Verifying this change

    XXXX

    Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

    • [x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
    • [x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
    • [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    • [x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
    • [x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.
    • [ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.
    opened by zhangjidi2016 2
  • [Issue #13] Rocketmq-Dashboard License

    [Issue #13] Rocketmq-Dashboard License

    Revert the front end resource license modification (c9d4cd1b727 / 635e0ce4d04) and exclude the front end folder from apache-rat-plugin. (front end resource license can be found in LICENSE file)

    What is the purpose of the change

    update Rocketmq-Dashboard License

    Brief changelog

    update Rocketmq-Dashboard License

    Verifying this change

    Manual test passed

    Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

    • [x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
    • [x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
    • [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    • [x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
    • [x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.
    • [ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.
    opened by StyleTang 1
  • Manage DefaultMQAdminExt objects using an object pool.

    Manage DefaultMQAdminExt objects using an object pool.

    Every time the mqAdminExt.xxx() method is called in the xxxServiceImpl, the aroundMQAdminMethod section of MQAdminAspect is executed to create the defaultMQAdminExt object and then destroy it. This causes frequent object creation and collection overhead.

    Object pools can be used for optimization, and object pools can be used to easily manage objects (retrieve, return, check for activity, check for availability, etc.), thereby reducing the overhead caused by frequent object creation to a certain extent

    enhancement 
    opened by zhangjidi2016 1
  • What is the difference between this and rocketmq console?

    What is the difference between this and rocketmq console?

    image

    ui is exactly the same

    opened by fsckzy 1
  • Use rocketmq-dashboard instead of rocketmq-console

    Use rocketmq-dashboard instead of rocketmq-console

    FEATURE REQUEST

    1. Please describe the feature you are requesting.

    Use rocketmq-dashboard instead of rocketmq-console

    1. Provide any additional detail on your proposed use case for this feature.

    Use rocketmq-dashboard instead of rocketmq-console

    1. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

    should-have

    1. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

    None

    opened by StyleTang 0
  • [#2] Use rocketmq-dashboard instead of rocketmq-console

    [#2] Use rocketmq-dashboard instead of rocketmq-console

    What is the purpose of the change

    Use rocketmq-dashboard instead of rocketmq-console

    Brief changelog

    Use rocketmq-dashboard instead of rocketmq-console. The config default value will keep using rocketmq console. (e.g. data path / log path)

    Verifying this change

    UT passed and manual test passed. image

    Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

    • [x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
    • [x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
    • [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    • [x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
    • [x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.
    • [ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.
    opened by StyleTang 0
  • [#707]Add permission control when loginRequired is true

    [#707]Add permission control when loginRequired is true

    What is the purpose of the change

    #707

    Brief changelog

    XX

    Verifying this change

    XXXX

    Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

    • [x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
    • [x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
    • [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    • [x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
    • [x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.
    • [ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.
    opened by zhangjidi2016 0
  • [ISSUE #19]Message track query enhancement

    [ISSUE #19]Message track query enhancement

    What is the purpose of the change

    #19

    Brief changelog

    XX

    Verifying this change

    XXXX

    Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

    • [x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
    • [x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
    • [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    • [x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
    • [x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.
    • [ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.
    opened by zhangjidi2016 0
  • Update README.md

    Update README.md

    fixed small typo error

    What is the purpose of the change

    fixed small type error

    Brief changelog

    1. change "apacherocketmq/rocketmq-console-ng" to "apacherocketmq/rocketmq-console" in README.md;
    2. change "apacherocketmq/rocketmq-console-ng:2.0.0" to "apacherocketmq/rocketmq-console:2.0.0" in README.md;

    Verifying this change

    Have checked the correct image name in docker hub (https://hub.docker.com/r/apacherocketmq/rocketmq-console)

    Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

    • [x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
    • [x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
    • [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    • [x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
    • [x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.
    • [ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.
    opened by charliex2 0
  • Message track query enhancement

    Message track query enhancement

    Currently, system topic (RMQ_SYS_TRACE_TOPIC) or message track defined in configuration files are used by default for message track query on the console. But now, users can specify specific topic to save message track information when sending and receiving messages on the client. If so, The console cannot query this message track information.

    image

    Can we select the previously specified message track topic before the user queries the message track information, like this? @StyleTang @vongosling

    image

    enhancement 
    opened by zhangjidi2016 3
  • [ISSUE #10] add react module for dashboard

    [ISSUE #10] add react module for dashboard

    What is the purpose of the change

    https://github.com/apache/rocketmq-dashboard/issues/10

    Separate the front-end and back-end modules and add react demo.

    You can build it by cmd below

    mvn clean package -Dmaven.test.skip=true
    java -jar target/rocketmq-dashboard-2.0.0.jar
    

    or just

     mvn spring-boot:run
    

    Then you can visit /app.html for previewing

    Brief changelog

    1. Add /frontend dir and add react code in it
    2. Add maven plugin for packaging all resource in one jar

    Verifying this change

    XXXX

    Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

    • [x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
    • [x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
    • [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    • [x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
    • [x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.
    • [ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.
    opened by RaymondCode 6
  • Choose and setup front end framework

    Choose and setup front end framework

    FEATURE REQUEST

    Please describe the feature you are requesting.

    Choose a new front end framework to maintain the web static resource.

    The current front-end and back-end mixed architecture is hard to maintain. We can find more information here. Front End / Back End Separate Solution

    Provide any additional detail on your proposed use case for this feature.

    We suggest to choose React as our front end framework, we can also add Redux and Redux related middleware Redux-Saga/Redux-thunk etc.

    We can introduce UI framework, something like ant-design dva umi (Free free to comment if you know better ones.)

    Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

    blocker. (Architecture upgrade strong dependence on it, we will migrate old front end page to this new framework)

    If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

    This is related to the front end / back end separate solution, but it can be done in parallel.

    opened by StyleTang 5
  • Front End / Back End separate solution

    Front End / Back End separate solution

    FEATURE REQUEST

    Please describe the feature you are requesting.

    Now the code of RocketMQ Dashboard mixed the front-end and back-end code together, the front-end architecture is too old, it is hard to maintain, for example, front end package is difficult to manage, the fancy features of the front-end framework cannot be used, can not add front end unit test etc...

    We hope to separate the front-end and back-end modules. The front-end choose React, uses npm to manage package, and the back-end continues to use Spring-boot and maven.

    This may introduce the deployment problem of front-end static resources. At present, we propose to use maven plugin to handle it. During the spring-boot packaging process, maven plugin should compile and package the front-end code and put it into spring-boot.jar. When deploying, only the spring-boot server needs to be deployed (It will contains the front end resource).

    Provide any additional detail on your proposed use case for this feature.

    We propose the rocketmq-dashboard package should like this.

    rocketmq-dashboard

    |-------src ( backend: Spring-boot)

    |-------frontend (React)

    When we execute package cmd, maven plugin should auto compile and release the front end resource, and build them into rocketmq-dashboard.jar

    mvn clean package -Dmaven.test.skip=true
    

    then we can run it just like a ordinary spring boot server.

    java -jar target/rocketmq-dashboard.jar
    

    Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

    blocker. (Architecture upgrade with separation of front and back ends strong dependence on it)

    If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

    This is related to the front-end architecture selection, but it can be done in parallel.

    opened by StyleTang 0
  • Are you using RocketMQ Dashboard?

    Are you using RocketMQ Dashboard?

    Are you using RocketMQ Dashboard?

    The state-of-the-art Dashboard of Apache RoccketMQ provides excellent monitoring capability. Various graphs and statistics of events, performance and system information of clients and application is evidently made available to the user. If you are using RocketMQ Dashboard, first we would like to Thank You. Here, we sincerely invite you to take a minute to feedback on your usage scenario.

    The purpose of this issue

    We are always interested in finding out who is using Dashboard, what attracted you to use it, how we can listen to your needs, and if you are interested, help promote your organization.

    What we would like from you

    Pls. submit a comment in this issue to include the following information:

    • your company, school, or organization
    • your country and city
    • your contact info, such as email, WeChat, and Twitter (optional).
    • usage scenario
    • expectations(optional)

    You can refer to the following sample answer for the format:

    * Organization: XX Company
    * Location: Seoul, South Korea
    * Contact: [email protected]
    * Version: v1.0.0
    * Status: production
    * Expectations(optional): Integrated with RocketMQ Operator, support diagnosis. 
    

    Thanks again for your participation! Apache RocketMQ Community

    opened by vongosling 3
Releases(1.0.0-beta)
Owner
The Apache Software Foundation
The Apache Software Foundation
human resourse management software

HRMS İstihdam ve Kariyer Platformu Proje İsterleri Req 1 : İş Arayanlar sisteme kayıt olabilmelidir. Kabul Kriterleri: Kayıt sırasında kullanıcıdan ad

Ceren Susuz 23 Aug 18, 2021
The Apache Software Foundation 39 Sep 12, 2021
This is an example of how conditional events can be triggered in Camunda using a simple spring boot project

Camunda Conditional Events Example This example is a Spring Boot Application using Camunda. In this example i'll show a variety of ways that BPMN's Co

Niall 4 Jun 6, 2021
A little of Java content every day for a hundred days.

100 Days of Java Table of Contents Day 1 - Generating a random number within a specific range. Day 2 - Formatting a LocalDateTime object. Day 3 - Sche

Helber Belmiro 43 Sep 11, 2021
GitactionBoard - Ultimate Dashboard for GithubActions.

Gitaction Board Gitaction Board - Ultimate Dashboard for GithubActions. Table of contents Usage Pull docker image Run docker image Configurations UI D

OTTO (GmbH & Co. KG) 11 Sep 7, 2021
A Spring Boot Camel boilerplate that aims to consume events from Apache Kafka, process it and send to a PostgreSQL database.

SPRING-BOOT CAMEL BOILERPLATE This is a Spring-Boot Camel Application model that you can use as a reference to study or even to use in your company. I

Bruno Delgado 45 Sep 17, 2021
Universal, flexible, high-performance distributed ID generator

CosId Universal, flexible, high-performance distributed ID generator 中文文档 Introduction CosId aims to provide a universal, flexible and high-performanc

Ahoo Wang 83 Sep 8, 2021
:fire: Spring-Boot-Plus is a easy-to-use, high-speed, high-efficient,feature-rich, open source spring boot scaffolding. :rocket:

Everyone can develop projects independently, quickly and efficiently! What is spring-boot-plus? A easy-to-use, high-speed, high-efficient, feature-ric

geekidea 2.2k Sep 8, 2021
Human Resources Management System

Human Resource Management System ( HRMS ) The following tools / languages will be used in this project; Java (Spring Boot based) - on the Backend side

Fatih Deniz 16 Aug 21, 2021
Two Spring-boot applications registering themselves to an spring-boot-admin-server application as separate clients for the purpose of monitoring and managing the clients

Spring-boot-admin implementation with 1 Server and 2 clients Creating a Server application to monitor and manage Spring boot applications (clients) un

null 5 Aug 28, 2021
All I know about Spring as a Spring Boot app

All about Spring This repository contains all the knowledge I have and all the things I can do with Spring You can download v1.0.0 java-doc here In th

Soroush Mehrad 8 Aug 14, 2021
Human Resource Management System - Backend

Human Resource Management System - Backend File Structure ??️ Layered Architecture Entities - The package in which the assets are kept DataAcces - Pac

Tarık Kaan Koç 26 Aug 14, 2021
:books: 本代码库是作者小傅哥多年从事一线互联网 Java 开发的学习历程技术汇总,旨在为大家提供一个清晰详细的学习教程,侧重点更倾向编写Java核心内容。如果本仓库能为您提供帮助,请给予支持(关注、点赞、分享)!

CodeGuide | 程序员编码指南 作者: 小傅哥,Java Developer, ✏️ 虫洞 · 科技栈,作者, ?? CSDN 博客专家, ?? Wiki阅读跳转(有目录) 本代码库是作者小傅哥多年从事一线互联网Java开发的学习历程技术汇总,旨在为大家提供一个清晰详细的学习教程,侧重点更倾

小傅哥 5.8k Sep 13, 2021
Official Elasticsearch Java Client

Elasticsearch Java Client The official Java client for Elasticsearch. Note: this project is still a work in progress. This client is meant to replace

elastic 40 Sep 7, 2021
Rewrite of the dataconverter system for performance.

DataConverter This mod completely rewrites the dataconverter system for Minecraft. Please note that this fabric mod is not to be used. It is published

null 23 Sep 1, 2021
Tuya 13 Sep 10, 2021
芋道 mall 商城,基于微服务的思想,构建在 B2C 电商场景下的项目实战。核心技术栈,是 Spring Boot + Dubbo 。未来,会重构成 Spring Cloud Alibaba 。

[toc] 友情提示:近期在升级和优化该项目,建议先 Star 本项目。主要在做几个事情: 1、微服务技术选型以 Spring Cloud Alibaba 为中心。 2、修改项目分层,并合并部分服务,简化整体服务的复杂性。 3、将管理后台从 React 重构到 Vue 框架。 交流群:传送门 前言

芋道源码 5k Sep 9, 2021
🎒 💻 Material for Computer Club Classes

MNNIT Computer Coding Club This repository contains the codes, support links and other relevant materials for every class under Computer Coding Club,

MNNIT Computer Club 60 Sep 13, 2021
SpringBoot show case application for reactive-pulsar library (Reactive Streams adapter for Apache Pulsar Java Client)

Reactive Pulsar Client show case application Prerequisites Cloning reactive-pulsar Running this application requires cloning https://github.com/lhotar

Lari Hotari 3 Sep 2, 2021