post: Architecture reduction post#78
Conversation
✅ Deploy Preview for loadsmart-engineering ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Co-authored-by: Welington Silva <welingtonms@users.noreply.github.com>
rodsenra
left a comment
There was a problem hiding this comment.
lgtm. We can later do a follow up post with the graph of microservices and the compute of complexity.
vbmendes
left a comment
There was a problem hiding this comment.
Great content, @gustahrodrigues. Congratulations!
I made minor neat-pick suggestions.
Co-authored-by: Vinícius Mendes <vbmendes@gmail.com>
Co-authored-by: Vinícius Mendes <vbmendes@gmail.com>
Co-authored-by: Vinícius Mendes <vbmendes@gmail.com>
Co-authored-by: Vinícius Mendes <vbmendes@gmail.com>
Co-authored-by: Vinícius Mendes <vbmendes@gmail.com>
| - We shut down all cloud resources associated with the service. | ||
| - Finally, we wrote thorough documentation explaining the reasons for decommissioning the service, focusing on the assumptions made during the process. | ||
|
|
||
| ### Results |
There was a problem hiding this comment.
Since this will be a public article, I would recommend making this section more generic to avoid exposing anything we don’t intend to share. For example:
We have decommissioned x% of the microservices supporting the Loadsmart Brokerage Business.
In terms of cost savings, we estimated a reduction of x% in cloud costs and x hours less of engineering work for maintenance. Considering the investment made, we expect a payback in less than x months.
It might be better to avoid using specific numbers or internal metrics, and instead keep the statements high-level. This helps maintain confidentiality while still communicating the overall impact.
Types of changes
Description of the proposed changes
Adding a new blog post describing our experience while optimizing the Brokerage services architecture.
Screenshots
Please include screenshots for UI changes