All Posts

Secure software refers to applications designed and developed with stringent security measures to protect against unauthorized access and vulnerabilities. It is foundational for maintaining customer trust, ensuring operational continuity, and mitigating financial and reputational risks. We need to look at this challenge as both top-down and bottom-up. In this blog we will explore the key aspects of building secure software, including metrics for tracking security, and the use of frameworks to enhance security.

Zero trust security is a security model that assumes all network traffic is untrusted, regardless of its source or destination. This approach requires strict verification of every request, regardless of whether it originates from inside or outside the network. In microservices architectures, where applications are composed of multiple independent services that communicate over the network, or across clouds, zero trust security is essential to protect sensitive data and prevent security breaches. In this article, we will explore how zero trust security can be implemented in microservices architectures to enhance security and protect sensitive data.

What does fitness mean to you? Every individual this question is asked to, will probably give a different answer. While one person may define fitness as the ability to run regularly, another might see it as simply being able to play with their grandchildren without fatigue and risk of injury. If we were to look at the common ground, it is about nurturing a body that can support and sustain us through our life. It is about the quality of life. In this blog, we will talk about the different components of fitness, small changes to help incorporate these in your life and finally micro workouts.

Creating microservices within the constraints of multi-tenancy, privacy and compliance can present challenges that need to be thought through. In this blog we will discuss some of these challenges especially around resource contention, data isolation, data governance and compliance, focussing on potential thought frameworks to consider.

Attempting to fit every component of a monolithic architecture into a microservice is like trying to fit a square peg into a round hole. Not everything belongs, and forcing it only distorts the integrity of both the structure and the function. In this blog we will provide a framework to identify which functionalities or modules are ripe for migration to a microservice and which are not.