Re: Microservices routing
Hello, itslave, you wrote: the C>> But here happens - in VPC the free addresses and machines came to an end die right after start. Or in ASG at Amazaona something broke. Well also can be and simply there is no the free capacity and ASG throws out Insufficient Capacity Error. I> Aha. And the atomic bomb fell to a data-center. And it is necessary to do all decisions taking into account these improbable events. So. Here recently such bomb fell to a data-center of one large company - at floor cleaning casually pushed a breaker and disconnected a supply for all data-center. . To argue about SLA and reliable systems, it is necessary to acquire at first that ALL breaks generally. For example, if it is a question about autoscaling', it so periodically : http://status.aws.amazon.com/rss/autosc east-1.rss Cs>> Existing machines are not capable to cope with a flow of requests, and frontend continues them to send. Lag backend' continues to rise. Clients frontend' panic, repeating operations even more often. Lag rises. Any client frontend' cannot soon receive results in time while backend processes already certainly unnecessary messages. I> Circuit breaker it is possible on a miscellaneous. Well as? I resulted the scenario of a standard failure of system of messages when it does only worse. A C>> How to do correctly? Very simply: to have a small operative store in capacity and to do handling so that at increase of loading handling time smoothly grew. At loading excess - actively to do load shedding, producing clients frontend' errors. I> it not the possible approach. To identify that not and to begin clients it is possible methods, the choice depends on specific requirements. Here I already "a choice depend on specific requirements" I hear again. HOW was specific to solve this problem with systems of messages, for example SQS? The C>> Well that is, a problem does not dare normally. I> once again. The unique criterion of normality of a solution of a problem is specifications. All. A point. Yes-yes. And to specifications it is, of course, written:" It is possible to break and lose the data if clients do too many requests ". If at you there such specifications I can sympathize only. In the real world, normality of the decision is defined exceptional by usage practice.>> What queue can do a C throttling the sending side? It is impossible to do it in SQS or ApacheMQ. I> Instead of it is necessary to do it in the approach offered by me. Well then I ask to describe how the problem with an overload in my scenario will dare. A C>> Approximately indeed. I> questions any more I have no Main method of sale of these Tibco looks so: comes and says that if the client buys Tibco/Oracle/whatever at it the member number of the nine of reliability magically increases. Thus brutal penal sanctions are registered in the contract for violations of it is monthly fee reset for the last month.