12 posts on Engineering.
Rehost, replatform, refactor, rebuild or replace: what each option costs relative to the others, how long it takes, what can go wrong, and how to decide per system instead of per portfolio.
Read moreThe five integration patterns compared on cost and fit, the system-of-record question that decides most designs, the failure modes we see most, and how to scope an integration before anyone quotes it.
Read moreThe six phases of a legacy data migration, the three-rehearsal rule, who has to sign off, what to do with data that is wrong in the old system, and how to run two systems side by side when you must.
Read moreThe signs that a move to microservices will pay for itself, the signs it will not, a comparison of monolith, modular monolith and microservices, and a decision rule based on team size and release pain.
Read moreWhat a cloud migration costs by scope, which applications should move first and which last, how run costs actually change, the risks that catch companies out, and what to measure once you are there.
Read moreA decision rule for the rebuild question based on three signals you can measure, not on how the code feels, and what a rebuild actually costs when you count the months.
Read moreThe one rule for MVP stack decisions, a default stack by product type, the choices that are hard to reverse, and why the fashionable option is usually the wrong one.
Read moreOur name comes from the OSI seven layer model. Here is why a networking reference model is a good metaphor for how we deliver software.
Read moreEvery vendor claims to be end-to-end. We break down the seven things that phrase has to cover before it means anything.
Read moreMost AI projects fail on integration, not on models. Our approach starts with the process, the data and the decision, and only then with the technology.
Read moreLegacy systems run the business, which is exactly why rewriting them all at once is dangerous. How we modernize incrementally while keeping operations running.
Read moreHIPAA, financial regulation and cryptography are not features to add later. What changes when compliance is a requirement from day one.
Read more