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*

5
  • Define customization. I think many decisions hinge on what specifically will be customized and how it will work. For example, storing a hex color code for the header in a database column versus the client wanting to completely redesign the interface. Commented Sep 28, 2021 at 20:48
  • 1
    This is typically handled with feature flags that can be enabled/disabled per tenant, but again, it depends on the level of customization. Commented Sep 28, 2021 at 20:50
  • Thanks for the feedback @DanWilson !, I already modified my question for you, you can find what I mean by customization under Edit section Commented Sep 28, 2021 at 21:28
  • Why not give all tenants the ability to choose between calculating price per unit or price per kilo? That way you avoid customizing anything and you add value for all of your tenants. (Also, you might consider offering that choice on a per product, not tenant, level) Commented Sep 29, 2021 at 17:11
  • 1
    My advice to anyone who asks here if a microservices architecture is the right choice for them is to build a monolithic app instead. If you have to ask, that means you’re not experienced enough to weigh the trade offs. A microservices architecture will introduce a lot of complexity and it’s likely you don’t actually have a single problem it solves. Commented Sep 29, 2021 at 17:44