It’s common to face challenges around long-running workflows, state management, and resiliency when you’re building cloud-native applications. Traditional approaches like background services or message queues might work sometimes, but they often require a lot of “glue code” and custom retry logic. This entails not only more work up-front for the developer, but also more maintenance in the long run.
That’s where Azure Durable Functions come in.
Security is the cornerstone of software built for regulated industries. Applications must work properly and meet strict compliance standards while protecting sensitive information at every stage. In healthcare, finance, and other regulated fields, secure Java development ensures data is safe, trust is maintained, and legal obligations are met. At Keyhole Software, we help teams build security into every part of …
One of the most significant shifts in enterprise software today is the move from monolith to microservices. Many see it as the path to agility and scalability, but it’s a transition that can be more complex than it first appears. In this post, we’ll share some of the key challenges and strategies we’ve learned along the way to help you …
The backbone of your business is often the enterprise applications you’ve relied on for years. But as time passes, you might start to question whether your software is still doing its job. Enterprise app modernization can help keep your systems efficient and ready for what’s next. In this post, we’ll cover the signs that it’s time to modernize, how to …
Developing custom applications is one of the hardest professional endeavors, and making them secure is even harder. Malicious actors are constantly changing tactics and strategies, which, unfortunately, makes it impossible to completely eliminate any security threat.
There needs to be a balance between delivering features quickly to meet business objectives and mitigating security risks. Thankfully, these two goals are not mutually exclusive. This blog post dives into the top mistakes that can be made while developing custom applications.
These recommendations are different from what would commonly be seen in an OWASP list, and they should be used in addition to whatever security practices and procedures are already in place by an organization’s infosec department. These recommendations are also written from an application architect’s (rather than an enterprise infrastructure) perspective, so most of them aren’t covered by existing security checklists.
