Download the PHP package apu/php-eureka-server without Composer

On this page you can find all versions of the php package apu/php-eureka-server. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package php-eureka-server

PHP Netflix Eureka Client

A PHP client for (Spring Cloud) Netflix Eureka service registration and discovery.

Installation

You can install this package using Composer:

composer require apu/php-eureka-server

Documentation

Create Eureka Client

The very first thing you need to do is to create an instance of EurekaClient using your own configuration:

List of all available configuration are as follows:

You can also change the configuration after creating EurekaClient instance, using setter methods:

Operations

After creating EurekaClient instance, there will be multiple operations to perform:

You can register your instance and send periodic heartbeat using start() method:

Using this method, first your service gets registered with Eureka using the configuration you have provided. Then, a heartbeat will be sent to the Eureka periodically, based on heartbeatInterval configuration value. This interval time can be changed just like any other configuration item:

It's apparent that this method should be used in CLI.

Discovery Strategy

When fetching instances of a service from Eureka, you probably get a list of available instances. You can choose one of them based on your desired strategy of load balancing. For example, a Round-robin or a Random strategy might be your choice.

Currently, this library only supports RandomStrategy, however, you can create your custom strategy by implementing getInstance() method of DiscoveryStrategy interface:

Then, all you have to do is to introduce your custom strategy to EurekaClient instance:

Local Registry and Caching

Failure is inevitable, specially in cloud-native applications. Thus, sometimes Eureka may not be available because of failure. In these cases, we should have a local registry of services to avoid cascading failures.

By default, if Eureka is down, the fetchInstance() method fails, so an exception would be thrown and the application cannot continue to work. To solve this problem, you should create a local registry of services.

There is an interface called InstanceProvider which you can make use of, by implementing getInstances() method of this interface and returning instances of a service based on your ideal logic.

In this example, we have cached the instances of the service in the Redis and are loading them when Eureka is down.

After creating your custom provider, just make it work by adding it to the configuration:

Your custom provider only gets called when Eureka is down or is not answering properly.

That's all you need to do. By adding this functionality, your application keeps working even when Eureka is down.

For caching all available instances of a specific service, you can call fetchInstances() method which fetches all of the instances of the service from Eureka:


All versions of php-eureka-server with dependencies

PHP Build Version
Package Version
Requires php Version >=5.4.0
guzzlehttp/guzzle Version ^6.3|^7.0.1
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package apu/php-eureka-server contains the following files

Loading the files please wait ....