John Folberth

Interested in learning more about cloud technologies, DevOps, and help improve community knowledge? Feel free to subscribe to my blog. blog.johnfolberth.com

One week until @BeerCityCode. Come check out my session on the latest developer experiences in Azure. Walk trough real world development workflows and experiences encompassing DevBoxes, Azure Deployment Environments, MCPs, and GitHub Coding Agent. github.com/JFolberth/ai-i…

@JohnLokerse @eddiejaoude 100%. Build a complete body of work to tell the story and illustrate your processes

@eddiejaoude I do! My blogs are documentation on how I have done things in the past or just to know how “something” works. Very handy! I recommend other people do this too, not only for yourself but for the community too.

Do you refer back to your previous blogs?

@housecor Azure Deployment Environments. Deploy your apps infrastructure in an ephemeral environment with the same IaC as prod. Started doing it for PRs to shift left. Then if need be, can reuse for integration into Azure Load Testing and other services.

I'm curious - Who's doing development with just two environments? (dev and prod) Would love to hear your experience and approach. If you have more environments, why do you feel they're necessary?

Working on a quickstart for anyone to be able to update an agent w/ their instructions and deploy a multi-tier chat application backed by Azure Foundry: github.com/JFolberth/ai-i… #AzureFoundry #Azure #GitHubCopilot

Missed the latest Build conference announcements on Azure, .NET, and AI? No problem, we have you covered Join us Tuesday, July 8 from 4:30 PM to 6:00 PM at @TeamBizStream. RSVP: meetup.com/grand-rapids-m…

Withing any DevOps process I have learned that over complication and unnecessary steps are typically the root of 90% of all pipeline issues.

🍻 Early bird pricing is up at beercitycode.com and ticket purchases are pouring in! Get yours now.

Latest post on managing SQL CI/CD similar to #Terraform in #AzureDevOps! This walkthrough covers ensuring your databases always match what is defined in source control while generating a 'plan' of any changes within your #cicid pipeline. #Azure techcommunity.microsoft.com/blog/healthcar…

When separate, the time spent in coordination and management of processes is a waste in human capital and introduces multiple risks and complexities.

To optimize on the success and speed of the cloud traditional solos need to be broken down. Teams have been successfully doing this for years.

Just need to throw it out there again. In the cloud, if you aren't deploying and managing application code together with infrastructure code should reevaluate your process.

Non technical overview on how to manage #AzureSQL Database Deployments like #terraform: techcommunity.microsoft.com/blog/healthcar… #devops #dataops

@housecor In this case running dotnet build command against a .sqlproj configurations to generate a different environment specific package: techcommunity.microsoft.com/blog/healthcar… For ADE here's a recent on use cases up to incorporating these environments in your CI pipelines: youtube.com/watch?v=1a3RBo…

@j_folberth I agree containers can simplify Not sure what sdk approach means in this context. Haven’t tried that Azure service

My preferred development workflow for 2024: 1. All devs have their own DB instance so we don’t conflict with each other. The DBs run locally, and can be reset via static SQL scripts via a single command. The SQL scripts are committed to source control. This way, we can code without internet, demo the app reliably, reproduce bugs, and write fast, reliable tests. 2. Create a short-lived feature branch for each ticket. Each pushed commit runs tests on CI. CI auto-deploys a dedicated ephemeral (short-lived) environment with a unique URL for each feature branch so people can test and approve *before* merge. Thus, no separate shared environments like UAT or staging are typically required. 3. When a PR is approved, we merge to main. The CI server auto-deploys the main branch to prod. If the feature isn’t ready for public use, hide it in prod via a feature flag.

Get to know SQL projects in their latest version with the msft.it/6019mCMJf.Sql project SDK - now on Data Exposed with @AnalyticAnna. Watch 📺: msft.it/6011mCMJ7 #AzureSQL

@AzhaAmir @AzureWeekly This article was not created by Chat GPT. The image by Bing Image creator. Would suggest clicking the article before posting such an assumption.

@AzureWeekly @j_folberth dont create with ChatGPT and put it as an article

Deploying .dacpacs to Multiple Environments via ADO Pipelines from @j_folberth buff.ly/48324ix #Azure

Got tired of not finding a good example of SQL CI/CD with YAML Pipelines. So....here's a new blog post on leveraging CI/CD for SQL Deployments in YAML Pipelines! techcommunity.microsoft.com/t5/healthcare-… #SQL #AzureDevOps #Pipelines #CICD #Azure

@svrooij Added your link to my latest blog post: techcommunity.microsoft.com/t5/healthcare-…

Putting together a new blog series around CI/CD for SQL Database developers.....does anyone know of any good version control introductions for data engineers I can reference? #SQL #git #AzureDevOps

@svrooij Thanks! I have a stub in there to automate the security role creation/provisioning via CI/CD by SQL script in the repo. I will refer to this for more details!