I write about Azure Functions over and over again because they are the perfect solution for what I am trying to do, small little things that I don’t want to spin up a larger unnecessary app to do it. Then I had a thought, why not have an Azure Function that I could http post to and sent an email from there…
I was recently working on a PWA application that utilizes SSO and one odd behavior that I noticed right off the bat was the fact that the SSO redirects forces the application to open a new window inside the browser instead of carrying the redirect inside the application shell. This is problematic as it defies the whole purpose of a PWA which attempts to make a web application feel native.
While on-premises, most applications did not take advantage of securing communications to the database on the wire just because of the inherent isolation advantages of having the application ONLY on the internal LAN. However, as more and more of these applications start moving to the cloud, the security of data over the wire is rightfully starting to gain increased importance.
The “lift-and-shift” approach with Azure IaaS can only deliver on small measure of the promise of agility and innovation in the Cloud when compared to modernized application (i.e., Cloud-optimized). Modernizing application with Azure PaaS, on the other hand, can deliver on the promise of agility and innovation to a great extent. It reduces the time required to manage the application and the time required to deploy a new release, and optimizes the speed to market.
While Cosmos DB offloads many of the hard NoSQL scaling problems, shaping your data and choosing a logical partition key are left to you. The partition key choice is arguably the most important decision you’ll need to make – it cannot be changed and must be determined upon creation of a collection.
In an agile development environment, there may be partially completed features or features with external dependencies that are not ready. Instead of relying on multiple code branches, instead you may opt for deploying code with a feature turned off. Later, that feature should be turned on via a configuration or database change. This post provides sample code that you can use to implement feature flags in your Angular app.
In a previous post I discussed an approach to handling backend redundancy using Azure API Manager (APIM). In this post I want to discuss the various options for providing a high-availability (HA) and disaster recovery (DR) to your services exposed by API Manager.
My customers have spent some time working with Azure Cosmos DB and had questions around pricing. I thought I would share a bit of what I have learned when it comes to pricing for Cosmos DB for this BLOG article.
Have you ever tried building an IoT solution on an embedded device like a Raspberry Pi with an ARM processor? What languages did you have to use? What if that device had to send data to the cloud for dashboarding and alerting? How would you build the dashboard and manage alerts for authorized users?
If part of this transition requires that aspects from the legacy process be kept, it’s a great opportunity to demonstrate that through the use of agile process and agile tools, we can have an even better control of the value (beyond just software) that the development team is creating for the company.