micro-service | Micro Service architecture | Microservice library

By default the broker will auto-create addresses and queues as required when a message is sent or a consumer is created by the core JMS client. These resources will also be auto-deleted by default when they're no longer needed (i.e. when a queue has no consumers and messages or when an address no longer has any queues bound to it). This is controlled by these settings in broker.xml which are discussed in the documentation:

• auto-create-queues
• auto-delete-queues
• auto-create-addresses
• auto-delete-addresses

To be clear, auto-deletion should not cause any message loss by default as queues should only be deleted when they have 0 consumers and 0 messages. However, you can always set auto-deletion to false to be 100% safe.

Queues representing durable JMS topic subscriptions won't be deleted as they are meant to stay and gather messages while the consumer is offline. In other words, a durable topic subscription will remain if the client using the subscription is shutdown without first explicitly removing the subscription. That's the whole point of durable subscriptions - they are durable. Any client can use a durable topic subscription if it connects with the same client ID and uses the same subscription name. However, unless the durable subscription is a "shared" durable subscription then only one client at a time can be connected to it. Shared durable topic subscriptions were added in JMS 2.0.

It turns out Godog doesn't trim the Steps from the feature files.

So, In my feature files, the steps for the above lines included:

When reading resource of id "ID1"_____(blank space)

The regex pattern therefore wasn't able to map the step definitions to these lines for some reason.

As soon as I removed the empty spaces, it worked great.

First, if you use reactor you shouldnt call blocking apis, as you did it in the save method. When you use webflux, you have a small number of threads and if you block those threads your application performance will be very poor. I suggest using reactive database driver instead.

1, You shouldnt use plane object in the controller, because you have to block the thread to get the object itself. In reactor, you mustnt call blocking operation. Also suggest to use blockhound if you are not sure about what is blocking. It will throw an exception during tests if blocking methods are called.

2, In reactive stream, you have to use the reactive operations, like map, flatmap, etc.. to do operations on your objects.

For example, suppose you want to go through a list of objects, load some data from web to each and save those into the database (note that here I'm going to use mock db and webservice, but you can change those into real services and the essence of the example is the processor. Also I use Kotlin here, which is similar to Java)

Understood the issue and found the solution.

Looks like the security hooks used in SpringBoot 1 are deprecated in SpringBoot 2. So in my micro-service B the below config in properties file wasn't working after upgrade

I managed to fix the problem with the help of Allard (see comments on question). The fix was to also persist the token after it has been claimed in the fetch() method. We also started making use of the replace() method supplied by the Couchbase SDK instead of the upsert() method, to better harness the CAS (Compare-and-Swap) optimistic concurency:

Well actually what you are describing is mostly close to the HTTP.

HTTP is synchronous which means that you have to wait for a response. The solution to this issue is AMQP as you mention. With AMQP you don't necessarily need to wait(you can configure it).

Its not necessarily a bad idea but what most microservices depend on is something called eventual consistency. As this will be a quite long answer with a lot of ifs I would suggest taking a look into Microservices Architecture

For example here is the part about the http vs amqp since its mostly a question about sychronous vs asychronous communication It goes into great detail about different approaches of microservices design listing pros and cons for your specific question and others.

For example in your case the Auth would happen at the API gateway as its not considered best practice to leave the microservices open for all the client applications.

Found a way, there is something called azurerm_api_management_api_operation_policy

https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/api_management_api_operation_policy

operation id is something you can get it from api-spec file, which uniquely identifies individual apis

It's definitely possible to do that. I've not done it with the log4j2 stack (I have with slf4j/logback), but the basic approach is:

• set those fields in the Mapped Diagnostic Context (I'm fairly sure log4j2 supports that)
• use a log appender which logs to logstash-structured JSON
• configure filebeat to ship the JSON logs
• if filebeat is shipping to logstash, you'll need to configure logstash to pass those preformatted JSON logs directly to elasticsearch

I assume the following from the information you provide:

• You have two Datatypes (Java classes). They should be merged together to one Java class
• You have to load this data from different sources
• Non of the classes are leading

I can provide you some example code. The code is based on the previos adoptions. This will give you an idea. It's not a simple copy and paste solution.

At first create a class with all fields you want to include in the result: