Bump logback-classic from 1.1.2 to 1.2.0 in /examples (#2076)

Bumps logback-classic from 1.1.2 to 1.2.0.

---
updated-dependencies:
- dependency-name: ch.qos.logback:logback-classic
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
1 file changed
tree: cf5db86c35dae010cb25a3de4935dc8003fcfcda
  1. .github/
  2. .mvn/
  3. docs/
  4. elasticjob-api/
  5. elasticjob-cloud/
  6. elasticjob-distribution/
  7. elasticjob-ecosystem/
  8. elasticjob-infra/
  9. elasticjob-lite/
  10. examples/
  11. src/
  12. .asf.yaml
  13. .gitignore
  14. .travis.yml
  15. LICENSE
  16. lombok.config
  17. mvnw
  18. mvnw.cmd
  19. NOTICE
  20. pom.xml
  21. README.md
  22. README_ZH.md
  23. RELEASE-NOTES.md
README.md

ElasticJob - distributed scheduled job solution

Official website: https://shardingsphere.apache.org/elasticjob/

Stargazers over time

ElasticJob is a distributed scheduling solution consisting of two separate projects, ElasticJob-Lite and ElasticJob-Cloud.

Through the functions of flexible scheduling, resource management and job management, it creates a distributed scheduling solution suitable for Internet scenarios, and provides a diversified job ecosystem through open architecture design. It uses a unified job API for each project. Developers only need code one time and can deploy at will.

ElasticJob became an Apache ShardingSphere Sub-project on May 28 2020.

You are welcome to communicate with the community via the mailing list.

License

GitHub release

Maven Status Build Status GitHub Workflow codecov Maintainability

Introduction

Using ElasticJob developers can no longer worry about the non functional requirements such as job scale out, so that they can focus more on business coding. At the same time, it can release operators too, so that they do not have to worry about high availability and management, and can automatically operate by simply adding servers.

ElasticJob-Lite

A lightweight, decentralized solution that provides distributed task sharding services.

ElasticJob-Lite Architecture

ElasticJob-Cloud

Uses Mesos to manage and isolate resources.

ElasticJob-Cloud Architecture

ElasticJob-LiteElasticJob-Cloud
DecentralizationYesNo
Resource AssignNoYes
Job ExecutionDaemonDaemon + Transient
Deploy DependencyZooKeeperZooKeeper + Mesos

Features

  • Elastic Schedule

    • Support job sharding and high availability in distributed system
    • Scale out for throughput and efficiency improvement
    • Job processing capacity is flexible and scalable with the allocation of resources
  • Resource Assign

    • Execute job on suitable time and assigned resources
    • Aggregation same job to same job executor
    • Append resources to newly assigned jobs dynamically
  • Job Governance

    • Failover
    • Misfired
    • Self diagnose and recover when distribute environment unstable
  • Job Dependency (TODO)

    • DAG based job dependency
    • DAG based job item dependency
  • Job Open Ecosystem

    • Unify job api for extension
    • Support rich job type lib, such as dataflow, script, HTTP, file, big data
    • Focus business SDK, can work with Spring IOC
  • Admin Console

    • Job administration
    • Job event trace query
    • Registry center management

Environment Required

Java

Java 8 or above required.

Maven

Maven 3.5.0 or above required.

ZooKeeper

ZooKeeper 3.6.0 or above required. See details

Mesos (ElasticJob-Cloud only)

Mesos 1.1.0 or compatible version required (For ElasticJob-Cloud only). See details