microservices

I'm trying to setup a MQTT Microservice using NestJS according to the docs . I've started a working Mosquitto Broker using Docker and verified it's operability using various MQTT clients. Now, when I start the NestJS service it seems to be connecting correctly (mqqt.fx shows new client), yet I am unable to receive any messages in my controllers. This is my bootstrapping, just like in the docs: main.ts async function bootstrap() { const app = await NestFactory.createMicroservice(AppModule, { transport: Transport.MQTT, options: { host: 'localhost', port: 1883, protocol: 'tcp' } }); app.listen(()

We are just researching a couple of API gateways, in particular Kong . Looking through their documentation it seems they support request/response transformation. However, if I understand this correctly, this seems limited to headers. Does Kong support API Aggregation like Netflix does it? No, by default one http request into Kong will only match to one upstream url. The Kong request and response transformation plugins handle simple Header, Body and Query String manipulation but Kong doesn't handle API aggregation. Obviously, Kong is very easy to modify via it's own plugin mechanism but

In a microservice architecture, we usually have two ways to communicate 2 microservices. Let’s say service A needs to get information from service B. The first option is an remote call, usually synchronous over HTTPS, so service A query an API hosted by service B. The second option is adopting an event-driven architecture, where the state of service B can be published and consumed by service A in asynchronous way. Using this model, the service A can update its own database with the information from the service B’s events and all queries are made locally in this database. This approach has the

I have a reliable dictionary in service fabric stateful service. I have a simple linq expression. I am using Ix-Async package for building an asyncenumerable. using (ITransaction tx = this.StateManager.CreateTransaction()) { var result = (await customers.CreateLinqAsyncEnumerable(tx)) .Where(x => x.Value.NameFirst != null && x.Value.NameFirst.EndsWith(n, StringComparison.InvariantCultureIgnoreCase)) .Select(y => y.Value); return await result.ToList(); } The data is organized into 2 partitions with around 75,000 records in each partition. I am using Int64 range as the partition key. In the

Currently i have a setup where my clients (web apps, iOS app etc) talks to my backend API .NET web app (Nancy) via REST calls. Nothing special. I now have a requirement to split this API up into microservices, where each service can be individually upgraded/deployed. My main API (public) will just perform authentication, then call into one of my microservices, which will be in my private network. What's the different ways i could communicate between my main API and other microservice API's? Pros/cons of each approach? The communication needs to be realtime - e.g request comes in from a browser

Say you have microservice A,B, and C which all currently communicate through HTTP. Say service A sends a request to service B which results in a response. The data returned in that response must then be sent to service C for some processing before finally being returned to service A. Service A can now display the results on the web page. I know that latency is an inherent issue with implementing a microservice architecture, and I was wondering what are some common ways of reducing this latency? Also, I have been doing some reading on how Apache Thrift and RPC's can help with this. Can anyone