Vendor selection: five criteria after the decision to buy
After the build-vs-buy call, five vendor criteria: exit cost, an SLA with teeth, an integration trial, support hours, and a reference of your size.
Topic guide
Architecture decisions with explicit trade-offs: monolith or microservices, when to scale, technical debt, rewrites, and build vs. buy.
3 topics · 12 articles
Proven patterns and how to record the decision.
After the build-vs-buy call, five vendor criteria: exit cost, an SLA with teeth, an integration trial, support hours, and a reference of your size.
A rewrite closes at three to five times the estimate. You decide with four inputs: test coverage, external coupling, who built the system, and business pressure.
A 5-engineer startup that adopts microservices trades one repository for four and one deploy for an orchestration job. A modular monolith carries the product further and keeps service extraction easy.
Aligned valuations and moving terms can collapse over one diligence report. The six dimensions reviewers measure, the findings that show up most, and who should run the process before the term sheet.
When and how to scale systems without losing reliability.
Teams that punish failure start hiding failure. Blameless post-mortems turn incidents into defenses against repetition.
Incident actions with an owner and a 30-day deadline, the old list reviewed every meeting, a focus on system causes, and the lesson published company-wide.
Five on-call design decisions: a nightly page cap, a six-line handover, a runbook before an alert goes live, and two cost metrics for the quarterly review.
Going from 10 to 50 engineers takes squads by domain, an internal platform team, a written decision guide, and a standing 15% capacity reserve for maintenance. The structure that changes speed within weeks and the metrics that show whether the product improved.
Choosing the right tool and dealing with legacy.
Building internally costs 4x the license price once you count the whole team. A decision tree with numbers on each side.
You cover recurring work with a person in the chair and a deadline-bound problem with a specialist for six weeks. Compare both costs before opening the role.
Without engineering numbers, the buyer finds the debt after signing and loses room to renegotiate. Five questions that fit in an afternoon, three ways to estimate the cost, and the contract mechanisms that close the gap.
Every sprint without a quality reserve grows debt until a one-week feature takes three. A method to map it, measure it, and decide what to pay first.
After proving the monolith is the bottleneck, whether for deployment, scale, or coordination between teams. That usually shows up around 30 engineers, not earlier.
A well-modularized monolith. Microservices add operational cost (deployment, observability, consistency) that a startup does not need to pay yet.
When there are more services than people able to be on call for them. For most mid-size companies, that lands between 5 and 15.
When reports and analytics start slowing down the transactional (OLTP) database. Before that, a read replica usually does the job.