4 posts tagged with "progressive delivery"

As you might have heard by now, the tech world is undergoing massive layoffs due to the looming recession. Big tech companies like Twitter, Meta, Google, and Amazon have all announced massive job cuts in the past few months. Software developers are on the receiving end in 2023, accounting for 20% of layoffs, according to data from workforce intelligence firm Revelio Labs.

Apart from the stress and anxiety it causes employees who were let go, layoffs can disrupt the rhythm of development teams and impact how projects move forward. The developers that survive layoffs are expected to keep everything running smoothly despite their smaller numbers. They'll have to explore strategies that will allow them to continue working efficiently and produce high-quality software without overworking themselves.

Feature flags are becoming a prominent part of DevOps practices and for good reason. They allow you to turn features in your live application on or off without redeploying code. You might think that something so powerful would require some rocket science-level programming to implement, but you'd be surprised to know that, at their core, feature flags are booleans and if-then-else statements.

Okay, that's an oversimplification of things, but it's true. And while there are different ways of implementing feature flags, they all share this common core. That said, let's take a broader look at feature flags and their uses in modern software development.

There’s nothing quite as exciting as seeing your app live on Google Play or the App Store. The culmination of months, if not years, of hard work can bring a sense of accomplishment, but with it comes the pressure of ensuring that your digital product functions as intended and meets the needs of your users.

Whether you’re planning to launch your first app or are a veteran in releases, you’re probably aware of the review process your app must go through before it can go live on the store. These reviews can take anywhere from a few hours to a few days, depending on the complexity of your app and the number of apps waiting to be reviewed.

Building a modern application often involves building it as a microservice, which provides developers with more flexibility and agility in terms of deployment options. However, deployment can either be a joy or a nightmare, depending on the strategy used, whether it's deploying microservices, testing new features, updating a business logic, or releasing a new version entirely? With every code change pushed, comes the risk of potential failures, which could be as a result of bad code quality or unexpected bugs, and this can potentially disrupt the user's experience.

Hence, picking an efficient deployment strategy is key to mitigating these deployment risks and not having to constantly disrupt your user’s experience by going into downtimes or completely having to go offline whenever there is something to be deployed.