Devops for Growth
107.5K views | +0 today
Follow
Devops for Growth
For Product Owners/Product Managers and Scrum Teams: Growth Hacking, Devops, Agile, Lean for IT, Lean Startup, customer centric, software quality...
Curated by Mickael Ruau
Your new post is loading...
Your new post is loading...

Popular Tags

Current selected tag: 'architecture monolithique'. Clear
Scooped by Mickael Ruau
Scoop.it!

Monolithic Transformation | VMware Tanzu

Monolithic Transformation | VMware Tanzu | Devops for Growth | Scoop.it
Part I: Fostering Change. Examine the principles of small-batch thinking, user-centric design, and shifting from functional teams to product teams.
Part II: Cloud Native Cookbook for Leadership. Apply those principles across your organization, from creating and communicating your strategy through building your pipeline and choosing the right cloud platform.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

The Majestic Monolith can become The Citadel

The Majestic Monolith can become The Citadel | Devops for Growth | Scoop.it
The vast majority of web applications should start life as a Majestic Monolith: A single codebase that does everything the application needs to do. This is in contrast to a constellation of services, whether micro or macro, that tries to carve up the application into little islands each doing a piece of the overall work.

And the vast majority of web applications will continue to be served well by The Majestic Monolith for their entire lifespan. The limits upon which this pattern is constrained are high. Much higher than most people like to imagine when they fantasize about being capital-a Architects.

But. Even so, there may well come a day when The Majestic Monolith needs a little help. Maybe you’re dealing with very large teams that constantly have people tripping over each other (although, bear in mind that many very large organizations use the monorepo pattern!). Or you end up having performance or availability issues under extreme load that can’t be resolved easily within the confines of The Majestic Monolith’s technology choices. Your first instinct should be to improve the Majestic Monolith until it can cope, but, having done that and failed, you may look to the next step.

That next step is The Citadel, which keeps the Majestic Monolith at the center, but supports it with a set of Outposts, each extracting a small subset of application responsibilities. The Outposts are there to allow the Majestic Monolith to offload a particular slice of divergent behavior, either for organizational or performance or implementation reasons.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Branching strategies: Git-flow vs. trunk-based development

Branching strategies: Git-flow vs. trunk-based development | Devops for Growth | Scoop.it
With Git platforms like Bitbucket, GitLab, GitHub, Azure DevOps offered on the cloud, it is now easier than ever to create code repositories on a platform that you prefer. Devbridge can help to choose the right platform in an unbiased way.
Mickael Ruau's insight:

 

Below, we compare git-flow vs. trunk-based noting key considerations for each.

Philosophy

Git-flow Trunk-based As far as possible from main branch As close as possible to main branch New features started from develop branch Short-lived feature branches started from main branch New release branch derived from develop branch, after stabilized release branch deployed Main branch always in a state ready to be deployed to production Only hotfixes derived from main branch Hotfixes start from main or release branch, need to be cherry-picked back to main

Team composition

Git-flow Trunk-based Lack of seniority within the team Well-composed and experienced team Working with other vendors/third-party Team augmentation model

Product type

Git-flow Trunk-based Complex, mature, monolithic product Microservices Brown-field product Modern single page application (SPA) / Mobile apps   Proof-of-concept (POC) / Prototype   Distributed system components

Authoring process

Git-flow Trunk-based Governed Team-driven

Deployment

Git-flow Trunk-based Various deployment models used Continuous Deployment practices recommended, such as feature toggles, quality gates, canary testing, self-service automation (e.g.. ChatOps), and monitoring

Release frequency

Git-flow Trunk-based Slower release cadence, pre-determined schedule Teams able to iterate quickly and independently

 

 
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

The Majestic Monolith

The Majestic Monolith | Devops for Growth | Scoop.it
Monolith by Rene Aigner Some patterns are just about the code. If your code looks like this, and you need it to do that, here’s what to do. You’d do well to study such patterns, as they give you a …
No comment yet.