Introduction Dependency validation helps to keep the code architecture clean and rules enforced. The video below gives a quick introduction to the dependency validation in Visual Studio. https://www.youtube.com/watch?v=w8kF3goKZPQ Recently a friend, asked about enforcing constraints in a project architecture, I explained this to him. But I haven't used it any of my previous projects (we're... Continue Reading →
Azure Cosmos Db has an impressive feature called 'Change feed'. It enables capturing the changes in the data (inserts and updates) and provides an unified API to access those captured change events. The change event data feed can be used as an event source in the applications. You can read about the overview of this feature... Continue Reading →
Disclaimer: This is not a post to discourage your next new thing, in fact as developers and technology decisions makers, we all have our own perils and survival dependency in Buzz engineering. But it is good to understand things, since there is an increasing noise around high technology churn and failures. So, what is Buzz... Continue Reading →
I came across the term 'Overambitious API Gateways' from Thought Works tech radar. The point is about, whether is it good or bad to have business logic in the API gateway? Since the term gateway is not a functional requirement and serves the purpose of reverse proxy; it is quite obvious that including business... Continue Reading →
Scheduled jobs are common in software systems, most of them perform some kind of a network or data related activity, outside the main execution context and triggered based on a timer event. There are several options available in Azure to implement scheduled jobs. Serverless options Azure Scheduler Azure Batch Custom code in VMs Before digging... Continue Reading →
Cloud has the proven promise of great opportunities for organizations & ISVs. Modern cloud platforms have low entry barriers and huge array service offerings beyond traditional enterprise application requirements. Cloud and the services provide intact environment to SaaS application providers with cutting edge innovation, agility and computational and storage scale for the global reach.
We keep the credentials and other secrets of the application in the source files. These secrets are visible to developers and being pushed to the source control. In order to avoid this, we can keep the secrets in centralized key management systems - but the credentials of the centralized key management system should be kept in the source files, resulting that at least one credential being placed in the source files. Let's see how to overcome this using Azure Managed Service Identity
Like a developer with little business context getting obsessed with the recent conference he attended and want to convert the systems to the great technology he saw there; the business stakeholders with little technical context love the the promise of high productivity and low cost of LCDPs As developers we favor the engineering feast of the solution more than the business solution. - I accept this; this does not mean we do not care the business, we do and make our fullest effort to solve the business problems but we do not like to do it at the stake of losing the passion of coding. - I know there can be many arguments on this point