Naresh WaswaniMicroservices Architecture, The Hard Parts : Are my services coupled ?In a Microservices Architecture, services are designed to conceal their internal implementation details and offer a clear interface for…Apr 142Apr 142
Naresh WaswaniMicroservices Architecture, The Hard Parts : Multiple Technology Stack — Boon or CurseMicroservices represent a form of Distributed Architecture that offers numerous advantages if implemented correctly. Some of these…Apr 73Apr 73
Naresh WaswaniMicroservices Architecture, The Hard Parts : Trap of Distributed MonolithWhen conversing with seasoned Senior Software Engineers who leverage Microservices Architecture for their product development, they…Mar 242Mar 242
Naresh WaswaniEvent Driven Architecture, The Hard Parts : Should it be Event or a Message ??If you happen to use Event Driven Architecture in your product, then I am sure you would have come across many situations where it was not…Mar 105Mar 105
Rahul vermaUnderstanding Swift’s Struct, Class, and the New ActorSwift empowers developers with diverse tools for managing data and concurrency. Among these champions stand structs, classes, and the newly…Feb 21Feb 21
Naresh WaswaniEvent Driven Architecture, The Hard Parts : Events Vs MessagesTeams new to Event-Driven Architecture often encounter confusion distinguishing between “Messages” and “Events.” Both constructs utilize…Feb 1813Feb 1813
Naresh WaswaniMicroservices Architecture, The Hard Parts : Data Query using CQRS PatternData Query involving multiple microservices to serve a single business use case is tough to design and implement. There are ways to handle…Feb 106Feb 106
Naresh WaswaniMicroservices Architecture, The Hard Parts : Data Query using API Composition PatternMicroservices Architecture is easy to visualize but hard to implement to take full advantage of it. A microservice owns the data and a…Feb 49Feb 49