News for hackers. Stuff that matters.
Re:MonolithFirst by wellpast on Wednesday June 03, 2015 @01:28PM (#9654324)
You are saying that you cannot have an architecturally sound software system when you do not fully know your domain. This is a fallacy. In fact, architectural soundness makes it MUCH easier (tractable) to grow your system in the face of changing your domain.
Re:MonolithFirst by dasil003 on Wednesday June 03, 2015 @02:28PM (#9654754)
How is it easier to change a service interface than an API within a single app? The former requires a specification and tooling around serialization/deserialization to have any meaningful guarantee of correctness, it requires error handling to reap the benefits of decoupling, the latter can be covered with a unit test.

I'm sorry but this is pure hype to say that microservices make refactoring easier: that is true if and only if your boundaries stay static. It is a huge assumption that anyone can draw those boundaries correctly for a large microservices architecture in its infancy.

Re:MonolithFirst by karmajunkie on Wednesday June 03, 2015 @01:52PM (#9654514)
That's not what I'm saying at all. You seem to be jumping to an assumption that all architectures are created equally at all points along the knowledge graph, or alternatively that a microservice architecture is fundamentally better than a monolithic architecture, and neither interpretation of that is true.