%PDF-1.7 1 0 obj << /Type /Catalog /Outlines 2 0 R /Pages 3 0 R >> endobj 2 0 obj << /Type /Outlines /Count 0 >> endobj 3 0 obj << /Type /Pages /Kids [6 0 R ] /Count 1 /Resources << /ProcSet 4 0 R /Font << /F1 8 0 R /F2 9 0 R /F3 10 0 R /F4 11 0 R >> /ExtGState << /GS1 12 0 R /GS2 13 0 R /GS3 14 0 R /GS4 15 0 R >> >> /MediaBox [0.000 0.000 595.280 841.890] >> endobj 4 0 obj [/PDF /Text ] endobj 5 0 obj << /Producer (dompdf 1.0.2 + CPDF) /CreationDate (D:20240908024216+00'00') /ModDate (D:20240908024216+00'00') >> endobj 6 0 obj << /Type /Page /MediaBox [0.000 0.000 595.280 841.890] /Parent 3 0 R /Contents 7 0 R >> endobj 7 0 obj << /Filter /FlateDecode /Length 1075 >> stream xVM6W̱H}&Hl聑hD:$퍁%Y[n^LkyfED(iC05zE+7uH 1Nx @*VįܭF1M&ӱVF*eИNp (Q?#a#7(݈apU;;|1- t}J%Krej(UE Y퀡7y/Ʒ=3R<H*$w˜ Gyz8Zx֦Y beW=XqLȍ ~ F:Y/mja^^m8JKJR*Q*Jw";dN0pt>gngM"9X)]Uv !žbYHhSاәLRN@ lPeάsC%kE J2Rd3k6ǹ"?I)rSp'} y aE 1($a7 ˒diw ݉P ¯F%jѐk8jrISn ?J$ r{mɳb""i`w;0R$K;`29 Y)%PtQͧ𰺿RN,FO()xV [WO(;ی3DT&W0 ) UxBcRf4/EԪ8| hv{m88P7 0 KFåbil/Cj|z%(珼@g܎4'&>4Wפȗ<'e-PZ#uMJSaIV endstream endobj 8 0 obj << /Type /Font /Subtype /Type1 /Name /F1 /BaseFont /Times-Roman /Encoding /WinAnsiEncoding >> endobj 9 0 obj << /Type /Font /Subtype /Type1 /Name /F2 /BaseFont /Times-Bold /Encoding /WinAnsiEncoding >> endobj 10 0 obj << /Type /Font /Subtype /Type1 /Name /F3 /BaseFont /Helvetica /Encoding /WinAnsiEncoding >> endobj 11 0 obj << /Type /Font /Subtype /Type1 /Name /F4 /BaseFont /Helvetica-Bold /Encoding /WinAnsiEncoding >> endobj 12 0 obj << /Type /ExtGState /BM /Normal /CA 0.3 >> endobj 13 0 obj << /Type /ExtGState /BM /Normal /ca 0.3 >> endobj 14 0 obj << /Type /ExtGState /BM /Normal /CA 1 >> endobj 15 0 obj << /Type /ExtGState /BM /Normal /ca 1 >> endobj xref 0 16 0000000000 65535 f 0000000009 00000 n 0000000074 00000 n 0000000120 00000 n 0000000372 00000 n 0000000401 00000 n 0000000550 00000 n 0000000653 00000 n 0000001801 00000 n 0000001910 00000 n 0000002018 00000 n 0000002126 00000 n 0000002239 00000 n 0000002298 00000 n 0000002357 00000 n 0000002414 00000 n trailer << /Size 16 /Root 1 0 R /Info 5 0 R /ID[<05e3df33ff232ef736bbc558b8b44a37><05e3df33ff232ef736bbc558b8b44a37>] >> startxref 2471 %%EOF What is Aggregator Pattern in Microservice - Spring Microservices

Spring Microservices

What is Aggregator Pattern in Microservice

by Leave a Comment

The aggregator design pattern is a service that receives a request and then makes requests of multiple services. Upon receiving the response, the service will then combine the results and responds to the initiating request.

In the Microservices world we constantly have to call various downstream systems in order to achieve desired functionality. Sometimes you will come across a requirement where you need to provide information to the upstream service, or pass a JSON response to the UI. Since you don’t have the information in your service domain, you will have to call various other downstream systems and cherry pick the required information from the responses, and the pass the JSON they are expecting.

Lets say you want to send a JSON response which has 20 fields. But your service only has 5 fields and in order to get the other 15 fields you have to invoke 3 different services. To address this problem, we need to implement the Aggregator pattern.

Post Views: 5,033

Reader Interactions

Leave a Reply

Your email address will not be published. Required fields are marked *