Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 2
    A good first step would be to split the system into multiple libraries, introducing seams. For now you're linking them together directly, but later you could wrap the libraries with a server and deploy them separately. Take care to design your libraries' APIs for very low coupling. No callbacks, no pointers, no shared data, nothing dynamic. Just data transfer objects that can be easily serialized. Copying isn't free, but it's cheap compared to distributed system overhead. When designing APIs, think up front about whether you're going to wrap it with HTTP+JSON, Kafka+Avro, gRPC, … Commented Jan 24, 2024 at 8:50
  • I'm not convinced that the separate modules you're addressing here should be independent microservices. Secondly, seriously consider if the effort of designing this hybrid system is not eclipsing the effort to just cut over to microservices directly, because I get the feeling that it very well might. Commented Jan 25, 2024 at 2:29
  • API, processing and storage sounds like horizontal layers to me. A microservice architecture will usually introduce vertical layers, where each service has its own API, its own storage and its own processing layer. Can you please clarify? Commented Jan 25, 2024 at 15:36