Comments for Plataformatec Bloghttp://blog.plataformatec.com.br
Plataformatec's place to talk about Ruby, Ruby on Rails and software engineeringWed, 11 Feb 2015 16:16:00 +0000hourly1http://wordpress.org/?v=4.0.1Comment on Introducing Discrete Integration by Danilo Caetanohttp://feedproxy.google.com/~r/PlataformaBlogComments/~3/i222jroFOFY/
Wed, 11 Feb 2015 16:16:00 +0000http://blog.plataformatec.com.br/?p=4420#comment-1470I really like about mechanisms that improves communication among the teams and people. Most initiatives like that should be used more inside the community.
]]>http://blog.plataformatec.com.br/2015/02/introducing-discrete-integration/comment-page-1/#comment-1470Comment on Introducing Discrete Integration by matheusmlhttp://feedproxy.google.com/~r/PlataformaBlogComments/~3/gjDrAfjpoXA/
Wed, 11 Feb 2015 00:45:00 +0000http://blog.plataformatec.com.br/?p=4420#comment-1469Awesome post. Really good approach for a common problem.
]]>http://blog.plataformatec.com.br/2015/02/introducing-discrete-integration/comment-page-1/#comment-1469Comment on Organizing microservices in a single git repository by Gustavo Dutrahttp://feedproxy.google.com/~r/PlataformaBlogComments/~3/eTQjOMVk3-0/
Tue, 10 Feb 2015 20:10:00 +0000http://blog.plataformatec.com.br/?p=4397#comment-1468I’d say it depends. You can deploy normally and make only the relevant services/microservices run on a given machine. Or, maybe, it can be part of the process to remove not used code from the deployed machine. It may differ from deploy tool to deploy tool, maybe I can help you better by asking if you have any specific deploy question.
]]>http://blog.plataformatec.com.br/2015/01/organizing-microservices-in-a-single-git-repository/comment-page-1/#comment-1468Comment on Introducing Discrete Integration by rcillohttp://feedproxy.google.com/~r/PlataformaBlogComments/~3/JxeWoP9iMII/
Tue, 10 Feb 2015 15:41:00 +0000http://blog.plataformatec.com.br/?p=4420#comment-1467Great post, Gustavo :clap:

I agree that improved communication, better branching management and smaller stories are a viable alternative to continuous integration. But there is still one case when feature toggle does seems to make sense. Other than the business toggle you provided as example. If building a whole new section inside an existing project, with multiple pages that only deliver value when a certain flow is complete, it’s still a good idea to frenquently merge each “100% developed page” of the flow into master and keep then hidden by a single routing toggle.

Otherwise we would be deploying features that do not deliver value. In my experience, not every feature is easily broken into incremental deliveries. Or we would keep an “epic branch” for quite sometime before merging into master.