3 ms·
Application code sets infra requirements, not vice versa. If infra shapes your application, it suggests tech limitations or significant mistakes. And I'm sorry
by lijok 3y ago
Application code sets infra requirements, not vice versa. If infra shapes your application, it suggests tech limitations or significant mistakes.
And I'm sorry, but without some concrete drawings you can't just claim current IAC creates low cohesion and strong coupling without making people suspect you don't know what those terms mean.
What would be very useful is an article covering the points of how testing works with Nitric, exactly how it saves you time and why the cost/benefit analysis of adopting Nitric makes sense.
- tholm 3y ago100% agree with your point on application code shaping infra, that's the standard pattern that tech like this is trying to achieve, by providing a standard by which those infrastructure requirements can be automatically understood. Fair point on the second, can I ask what you specifically mean by concrete drawings? I'd really like to understand your perspective on separation of concerns between IaC and application code better. Thanks for content takeaway as well I really appreciate the feedback. The closest thing we have right now is a published customer use-case: https://nitric.io/case-studies/dropbio https://nitric.io/case-studies/dropbio but I don't think this hits the mark for what you're after.