I am not clear on what type of services can be scaled when using Service Grid.
The docs talk about, Custom Counters, Hierarchical Maps, ID Generators etc as some type of services. In my scenario, i have multiple business micro services implemented using the Spring Boot framework. Does the Service Grid help in scaling each of these micro services based on the load. Basically, based on the load or some suitable algorithm would they instantiate and deploy an instance of a micro service so that failover is avoided ,without impacting the client. In a typical scenario, when a Service Registry like Eureka is being used, each and every service will register with the service registry and also periodically send a heartbeat so that they remain active. Is that sort of functionality provided when using Service grid. Can we consider using Service Grid instead of a Service Registry like Eureka for scaling and load-balancing of micro services. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Service-Grid-vs-Service-Registry-like-Eureka-Consul-tp8104p8159.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
