Operations | Monitoring | ITSM | DevOps | Cloud

Container technology is considered one of the most rapidly evolving in the software industry's recent history. There has been a seismic shift towards more and more organizations adopting containerization for their applications. Containers offer a lightweight, portable, and more efficient alternative to virtual machines and help us run software securely and reliably across different server environments.

In pursuit of staying competitive in the market, many organizations choose speed over quality resulting in the accumulation of technical debt. This blog will dive deep into the concept of technical debt and explore ways to remediate it.

Mattermost Playbooks help software engineering teams orchestrate their work across all tools and teams to plan projects and hit milestones by uniting your tech stack through a single point of collaboration. We want to see how our community is leveraging Playbooks in their own tech stack and share your creations with everyone so the whole community benefits. We’re doing this by launching a new effort to commission original blog articles that show Playbooks in action.

Chris Yates is a Senior Vice President, Managing Director at Republic Bank, one of the most innovative and forward looking banks in the US. For the last five years and more, he and the bank have been working to introduce DevOps to their database development process. Along the way he has had the opportunity to be joined on his DevOps journey by several of his colleagues who have played an instrumental part in enabling cross collaboration among the development teams.

You can subscribe to Break Things on Purpose wherever you get your podcasts. In this episode of the Break Things on Purpose podcast, we speak with Sam Rossoff, Principal Software Engineer at Gremlin.

The year is over, and the word ‘Observability’ has been one of the buzzwords that kept everyone checking throughout the year for deserving reasons. The organizations do not want to leave any stone unturned to maintain performance and offer robust services from ‘monitoring’ practices to ‘observability’, ‘telemetry’, and visibility capacities. So let’s get into the meaning of each term and understand how they are vital for business growth.

In part 1 of this series, we looked at common design principles and patterns for assembling microservices in serverless environments. But when it comes to building serverless applications, designing your architecture is only part of the challenge. You also have to ensure that each of your individual functions and services are secure, reliable, and highly performant—without incurring enormous costs.

Serverless has become an increasingly popular paradigm among organizations looking to modernize their applications as it allows them to increase agility while reducing their operational overhead and costs. But the highly distributed nature of serverless architectures requires developers to rethink their approach to application design and development. AWS-based serverless applications hinge on AWS Lambda functions, which are stateless and ephemeral by design.