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.

Required fields*

4
  • 2
    The 5-10 files to 70-100 files is a bit more than a hypothetical. My last task was to create some functionality in one of our newer microservices. The new service was supposed to receive a request, and save a document. In doing so, I needed classes to represent the user entities in 2 separate databases and repos for each. Repos to represent other tables I needed to write to. Dedicated classes to handle file-data checking and name-generation. And the list goes on. Not to mention, every class that contained logic was represented by an interface so it could be mocked up for unit tests. Commented Jul 9, 2019 at 14:07
  • 1
    As far as our older codebases, they are all tightly coupled and incredibly monolithic. With the SOLID approach, the only coupling between classes has been in the case of POCOs, everything else is passed through DI and interfaces. Commented Jul 9, 2019 at 14:09
  • 3
    @JDDavis - wait, why is one microservice working directly with multiple databases? Commented Jul 9, 2019 at 15:35
  • 1
    It was a compromise with our dev manager. He massively prefers monolithic and procedural software. As such, our microservices are a lot more macro than they should be. As our infrastructure gets better, slowly things will move into their own microservices. For now we're somewhat following the strangler approach to move certain functionality out into microservices. As multiple services need access to a specific resource, we are moving those into their own microservices as well. Commented Jul 9, 2019 at 15:45