Spring Boot Microservices Guidance both soap and XML configaration there and jboss serve also
Budget: ₹100 – ₹400 INR
I’m working on a Java Spring Boot micro-services application and need a seasoned hand to straighten out a few points and help me close some production Jira tickets.
Most of my questions revolve around how the services talk to each other—specifically, how data moves between them in both synchronous calls (REST, gRPC or similar) and asynchronous flows (message queues, Kafka, etc.). I’d like you to walk me through the current interaction patterns, point out bottlenecks or anti-patterns, and suggest improvements.
At the same time, I’ll share a small batch of Jira issues that are already reproduced in our lower environment. They typically involve cross-service data consistency or timing problems. Your role is to propose—and, if feasible within the scope, demo—clean, production-ready solutions that I can implement or merge.
Deliverables
• A concise explanation (meeting notes, annotated diagram, or short write-up) of existing data-flow paths for both sync and async calls
• Actionable recommendations or code snippets that resolve each provided Jira ticket
• A brief Q&A or screen-sharing session to ensure the fixes are fully understood
Tech stack keywords you should know: Java 17, Spring Boot 3.x, Spring Cloud, REST, gRPC, Kafka/RabbitMQ, Docker, Kubernetes.
If you’re confident debugging service interactions and can articulate clear, pragmatic solutions, I’m ready to get started right away.
Most of my questions revolve around how the services talk to each other—specifically, how data moves between them in both synchronous calls (REST, gRPC or similar) and asynchronous flows (message queues, Kafka, etc.). I’d like you to walk me through the current interaction patterns, point out bottlenecks or anti-patterns, and suggest improvements.
At the same time, I’ll share a small batch of Jira issues that are already reproduced in our lower environment. They typically involve cross-service data consistency or timing problems. Your role is to propose—and, if feasible within the scope, demo—clean, production-ready solutions that I can implement or merge.
Deliverables
• A concise explanation (meeting notes, annotated diagram, or short write-up) of existing data-flow paths for both sync and async calls
• Actionable recommendations or code snippets that resolve each provided Jira ticket
• A brief Q&A or screen-sharing session to ensure the fixes are fully understood
Tech stack keywords you should know: Java 17, Spring Boot 3.x, Spring Cloud, REST, gRPC, Kafka/RabbitMQ, Docker, Kubernetes.
If you’re confident debugging service interactions and can articulate clear, pragmatic solutions, I’m ready to get started right away.