This week I have been using Claude Code and Windsurf side by side. I would make change with one, stash it, ask the other for similar change and then would diff it.
Overall Windsurf was pretty on a par with Claude code.
12 karma · joined April 16, 2017
This week I have been using Claude Code and Windsurf side by side. I would make change with one, stash it, ask the other for similar change and then would diff it.
Overall Windsurf was pretty on a par with Claude code.
- smaller blast radius: every change is small and specific to service so easy to rollback and understand the impact
- load tests: capacity management was relatively easy; small services with small dependencies
- easier to update dependencies: java version updates was not huge project with every feature development on hold
- autonomy: team had more autonomy as it didn’t require committee approvals
- prolific design patterns: services could use different architectural patterns
This obviously came with lot of other issues - latencies, cross service atomocity, logs correlation. But at the end I believe pros outweigh the cons and I would continue to use SOA pattern wherever I could.
Industry has been trending towards microservices/lambdas which in my opinion take it too far. Finding that balance between Monolith and micro service is what works in my opinion.
I have over 15+ years of professional development experience and AWS experience and I understand the scale.
Our company has 20-30 instances used by 5-6 services. We use terraform/ansible to deploy infrastructure so deploys are pretty reliable and repeatable. So I am genuinely interested to understand if it’s worth going container route?
With expanding family, I have been contemplating a lot to move outside of CA for cost saving but thoughts about racial issues plaguing the country just makes me nervous.