Skip to main content
29 votes

How to maintain dependencies shared among microservices?

Combine the dependency and the cluster of micro-services into one monolith. Adopting microservices should be about enabling independent development and deployment of individual parts, reducing ...
bdsl's user avatar
  • 3,776
18 votes

How to maintain dependencies shared among microservices?

Exported methods should be part of a stable API, which means that you never change the signature of a method once it is published, unless you create a new major version of the library. If you use the ...
Hans-Martin Mosner's user avatar
8 votes

How to maintain dependencies shared among microservices?

There really is no easy way to resolve this. The microservices are coupled at a much deeper layer than they should be. Reducing the maintenance cost means properly decoupling these things so that ...
Greg Burghardt's user avatar
7 votes
Accepted

Adding a CLI to a Windows service

This is a classic separation of concerns. You have one use-case for a process that runs as a headless Windows service performing tasks. You have a second use case for a CLI tool parsing command line ...
Avner Shahar-Kashtan's user avatar
6 votes

How to Handle Large File Uploads in Angular and Hibernate Without Exceeding HTTP Request Size Limit?

HTTP requests most definitely can be configured on the server side to be limitless. However that won't help you much because JSON cannot be processed as a stream, or at least it is hard. Typically ...
freakish's user avatar
  • 1,926
5 votes

Adding a CLI to a Windows service

What you're describing sounds an awful lot like most DBMSes. For example, the MySQL Service process, mysqld, runs independently and does all the heavy lifting. It's Command Line Interface, mysql, ...
Phill  W.'s user avatar
  • 12.5k
4 votes

How to maintain dependencies shared among microservices?

TL;DR: Change the signature and don't upgrade until ready. I am, actually, in a similar situation at work, and it's an architecture I chose. In order to protect IP, our codebases are organized in the ...
Matthieu M.'s user avatar
  • 15.1k
3 votes

REST API with swappable backends

Your last 2 paragraphs are the way to go. No real overhead, especially if you cache any client specific meta data associated with each call. Most likely you will have to write a fa├žade for each back ...
LoztInSpace's user avatar
  • 1,199
2 votes
Accepted

Need help on Clean Architecture with Service/Manager/Controller

I believe 2 is more in keeping with the Clean Architecture, Onion, Ports and Adapters, Hexagonal philosophy. This does leave your use case code feeling fairly brainless. String comes in, string goes ...
candied_orange's user avatar
2 votes

How to maintain dependencies shared among microservices?

I think there are two main ways to think about this and how to deal with it. One is that when you have a shared library in your code base, you need to really think about managing it the way an open-...
JimmyJames's user avatar
  • 27.8k
1 vote

How to maintain dependencies shared among microservices?

Put all your code - services+libraries - in a monorepo You've hit the classical problems with micro services. A better way would be to manage your project as a monorepo - a single repo, but managed ...
Jonathan's user avatar
  • 519

Only top scored, non community-wiki answers of a minimum length are eligible