Knowing the takeaways
In this section, we will abstract a bit from the specific patterns and instead try to pull out the wider learning points you can use in your day-to-day work as a Salesforce architect or in preparing for the CTA Review Board.
When architecting Salesforce solutions, you should be mindful of the following:
- Middleware can be a great way to create order and improve the structure of your system landscape. However, you can also use it in ways that do more harm than good.
- If all you are doing is replacing point-to-point connections with equivalent one-to-one flows through the middleware, you are probably in anti-pattern territory.
- Custom services can be a great addition to your Salesforce org in certain cases. However, they come with considerable added complexity.
- You should never reflexively add lots of custom services because they seem to be what the business is calling for. Instead, take a step back and look at the big picture of requirements...
