<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by azeem olatunji on Medium]]></title>
        <description><![CDATA[Stories by azeem olatunji on Medium]]></description>
        <link>https://medium.com/@azeemolatunji?source=rss-418bd47d2f8a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*dnPvVClW0S1DLtf8</url>
            <title>Stories by azeem olatunji on Medium</title>
            <link>https://medium.com/@azeemolatunji?source=rss-418bd47d2f8a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:52:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@azeemolatunji/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[DIFFERENCE BETWEEN AZURE FUNCTION AND AZURE LOGIC APP]]></title>
            <link>https://medium.com/@azeemolatunji/after-conducting-extensive-research-to-prepare-for-az204-i-struggled-to-differentiate-between-47a4226c6949?source=rss-418bd47d2f8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/47a4226c6949</guid>
            <dc:creator><![CDATA[azeem olatunji]]></dc:creator>
            <pubDate>Sat, 22 Apr 2023 14:40:19 GMT</pubDate>
            <atom:updated>2023-04-22T15:02:45.866Z</atom:updated>
            <content:encoded><![CDATA[<p>DIFFERENCE BETWEEN AZURE FUNCTION AND AZURE LOGIC APP</p><p>After conducting extensive research to prepare for AZ204, I struggled to differentiate between Azure Functions and Logic Apps. In order to clarify my understanding, I decided to write a brief story about each of them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/321/1*OAEKd1AmdtvAR0t1T6jBig.png" /><figcaption><strong>Azure Function</strong></figcaption></figure><p>Azure Functions is a serverless computing service that allows you to run code on-demand without worrying about managing the infrastructure. It enables you to build and deploy event-driven, scalable, and cost-effective applications that can handle a wide range of tasks, from simple to complex.</p><p>With Azure Functions, you can write your code in several programming languages, including C#, Java, JavaScript, Python, and PowerShell, and execute it in response to various triggers such as HTTP requests, events, timers, and message queues. Functions can also integrate with other Azure services, such as Azure Event Grid, Azure Cosmos DB, and Azure Blob Storage.</p><p>In summary, Azure Functions is a powerful tool that enables developers to build and run applications in a serverless environment, with the ability to scale up or down depending on demand easily.</p><p><strong>Use Case of Azure Function</strong></p><ol><li>Event-driven processing: Azure Functions can be triggered by events from different sources such as message queues, event hubs, or blobs. This makes it suitable for building serverless applications that respond to events in real-time, such as processing orders, sending notifications, or analyzing data.</li><li>Webhooks and APIs: Azure Functions can act as webhooks or APIs to integrate with other applications or services. They can receive HTTP requests and execute custom code to perform tasks such as data validation, authentication, or processing.</li><li>Scheduled tasks: Azure Functions can be scheduled to run at specific times or intervals, allowing you to automate tasks such as backups, data processing, or sending reports.</li><li>Chatbots: Azure Functions can be used to build chatbots that interact with users in real time, using natural language processing and other AI services.</li><li>Serverless workflows: Azure Functions can be used in conjunction with other Azure services such as Logic Apps or Event Grid to build complex workflows that automate business processes or respond to events.</li></ol><p>In summary, Azure Functions can be used in a wide range of scenarios, from simple event processing to complex serverless workflows, providing developers with a flexible and scalable platform to build and deploy their applications.</p><p><strong>Azure logic app</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*2kYdgcRC9yn0Arr5vjAWeg.png" /><figcaption>Azure logic app</figcaption></figure><p>Azure Logic Apps is a cloud-based service that provides a way to build and run scalable workflows that integrate with various systems, services, and data sources. With Logic Apps, you can easily create and manage workflows using a visual designer, without having to write code.</p><p>Logic Apps supports more than 200 connectors that allow you to connect to various services, including SaaS applications, on-premises systems, and other Azure services. You can use these connectors to build workflows that automate business processes, such as sending emails, processing data, triggering alerts, or posting messages to social media.</p><p>Logic Apps also provides a wide range of built-in triggers and actions that can be used to create workflows, as well as support for custom connectors and APIs. You can also use Azure Functions or other code-based services within Logic Apps to extend its capabilities.</p><p><strong>Use Case of Azure Logic Apps</strong></p><p>Azure Logic Apps can be used for a variety of use cases, some of which include:</p><p>1. Data integration: Logic Apps can be used to integrate data from various sources such as SaaS applications, on-premises systems, and other Azure services. You can use connectors to build workflows that automate data extraction, transformation, and loading (ETL), as well as synchronization between systems.</p><p>2. Business process automation: Logic Apps can be used to automate complex business processes that involve multiple systems and stakeholders. You can use workflows to orchestrate tasks such as approvals, notifications, escalations, and error handling.</p><p>3. Monitoring and alerting: Logic Apps can be used to monitor systems and services and trigger alerts based on predefined conditions. You can use connectors to retrieve data from systems such as Azure Monitor or Application Insights and build workflows that send notifications or perform other actions based on the data.</p><p>4. IoT integration: Logic Apps can be used to integrate with IoT devices and services, such as Azure IoT Hub, to automate tasks such as data processing, analysis, and visualization.</p><p>5. Chatbots and AI integration: Logic Apps can be used to integrate with chatbots and AI services such as Azure Cognitive Services or Bot Framework to build intelligent workflows that respond to natural language requests and perform tasks such as sentiment analysis or language translation.</p><p>In summary, Azure Logic Apps provides a versatile platform for building and managing workflows that can automate business processes, integrate with various systems and services, and leverage advanced technologies such as AI and IoT.</p><p>Difference Between Azure Function and Azure Logic App</p><p>Here are some key differences between Azure Logic Apps and Azure Functions:</p><p>Azure Logic Apps:<br>- Designed for building and managing workflows using a visual designer<br>- Provides a wide range of connectors and built-in triggers and actions for integrating with various systems and services<br>- Can handle long-running workflows that involve multiple steps and external systems<br>- Suitable for building complex business processes that involve multiple stakeholders and systems<br>- Supports monitoring and alerting, as well as error handling and retry policies</p><p>Azure Functions:<br>- Designed for running code in response to events or triggers<br>- Provides support for various programming languages and allows you to write custom code<br>- Can handle short-lived tasks and functions, such as data processing or data transformations<br>- Suitable for building microservices and serverless architectures<br>- Supports scaling up or down automatically based on demand, and can be cost-effective for certain workloads</p><p>In summary, Azure Logic Apps is a platform for building and managing workflows that integrate with various systems and services, while Azure Functions is a platform for running code in response to events or triggers. Both services have their unique use cases and can be used in conjunction with each other to build powerful and scalable applications.</p><p>Resources:</p><p>Microsoft, Serverless360</p><p><a href="https://learn.microsoft.com/en-us/training/paths/implement-azure-functions/">AZ-204: Implement Azure Functions - Training</a></p><p><a href="https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-overview">https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-overview</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47a4226c6949" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Azure Devops]]></title>
            <link>https://medium.com/@azeemolatunji/azure-devops-d283907fa1d0?source=rss-418bd47d2f8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d283907fa1d0</guid>
            <category><![CDATA[pipeline]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[microsoft-azure]]></category>
            <dc:creator><![CDATA[azeem olatunji]]></dc:creator>
            <pubDate>Wed, 07 Sep 2022 09:28:46 GMT</pubDate>
            <atom:updated>2022-09-07T09:28:46.415Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Ome-oSxDNx7mQxJFZJ-NJg.png" /><figcaption>Azure Devops</figcaption></figure><p><strong>What is Azure Devops?</strong><br>Hello, in this article I will try to explain Microsoft&#39;s Azure DevOps product. Before starting to explain Azure DevOps, it would be better to go over some basic concepts. Let&#39;s start with &#39;Software Lifecycle&#39;.<br><br><strong>SDLC — Software Lifecycle</strong><br>(Software Development Life Cycle (SDLC) — Software Development Lifecycle)<br>Every software project should have these three phases: These are sometimes intertwined, sometimes separate, depending on the project.<br>These:<br>-Planning (Project management)<br>-Development(Source control)<br>-Operation (Build and development)<br>So, if we show it in a flow, we can say that the process in software development goes like this: Develop -&gt; Test -&gt; Build -&gt; Deploy<br><br><strong>DevOps</strong><br>Words are not enough to describe DevOps, of course, but we can briefly define it as providing continuous value by bringing people, processes and technologies together. You can check this video for detailed information.<br><a href="https://www.youtube.com/watch?v=0yWAtQ6wYNM">https://www.youtube.com/watch?v=0yWAtQ6wYNM</a></p><p><strong>CI/CD</strong><br>(CI-Continuous Integration, CD is Continuous Delivery)<br><br>The software will continue to evolve. When we make changes to the project during this process, we want these changes to be included in the live environment as soon as possible after passing the necessary tests and controls, which we call CI/CD.<br>For example, let&#39;s say we are going to make our project live on a container. After the development phase,<br><br>We need to go through Code -&gt; Test -&gt; Build Image -&gt; Push Repo -&gt; Deploy -&gt; Release and these steps are repeated for each change. It&#39;s almost like a loop.<br><br>For now, we can consider that Code-Test-Imaging-Creating Repo CI, Deploy and Release are included in the CD part for now. However, it would be more correct to think of these processes as an interlocking chain.<br><br>So what can we use in the management of these processes?<br>There are loads of solutions for every need and every part of the software development cycle. You can use separate technologies for each development step. For example, Jira/Slack for planning-communication step, Github for version control-ci-build, Jenkins; a different tool for deployment etc. this is how it will go. There may be a downside to this approach, how to make the connection between processes. For that too…</p><p><strong>Azure DevOps</strong><br>It&#39;s a nice platform that can help us.<br>We can automate all these processes from a single environment, including development with Azure and Azure Devops. In other words, when we make a change in a project and push the change to the git repo, Azure runs all these stages that we have forwarded in the configuration without doing anything, and if the result in these stages is successful, we can see the change in live without doing all these stages manually.<br><br>While talking about software development processes, we initially divided it into 3 basic stages. Plan-Development-Operation, in other words Plan-Dev-Ops. Azure DevOps offers solutions for all of these processes in one place.<br><br>What other advantage does Azure give us?<br><br>- All end-to-end services are integrated.<br>- The size of the team and the project is unimportant. Scalable<br>- On-prem, hybrid, cloud can be used in any environment.<br>- Support is available when needed.<br>- Admin and access controls are consistent.<br><br>Where can we use Azure DevOps in SDLC processes?<br><br>-For planning; Azure boards<br>-Development; Azure repos<br>-Operation; Deployment: We can deploy to Azure itself, as well as use deployment and other processes in environments such as AWS, Google Cloud or On Premise.<br><br>To briefly introduce some services, let&#39;s take a look at our first service, Azure Boards.</p><p><strong>Azure Boards</strong><br>Planning part One of the most important parts of SDLC and DevOps process, Azure Boards, which is one of the planning features of Azure DevOps, is a very nice feature in this planning, teamwork and task management.<br>In addition to having many features such as creating Agile and Scrum tables, planning, and assigning all features to a task on the board, workpieces/tasks can be defined to individuals/groups, just like in Jira.<br>Here, too, we can plan our processes on kanban tables by drag-and-drop on the same web interface.<br><br>In summary, with Azure Boards;<br>-Test plans etc. plans can be made.<br>-We can get information about the status of the project thanks to the analysis tools.<br>-Moreover, it is linked to all other Azure DevOps services and services like Github.</p><p><strong>Azure Repos</strong><br>Azure Repos can be thought of as a git repo, it has all the features of other git solutions. Source control, git flow and even all features on this side can be linked to the work plan in Azure Boards. You can also implement your existing repo in services such as Github here. Being able to edit your code via the browser also allows you to develop on your mobile devices such as tablets. For more information about Azure Repos, see <a href="https://docs.microsoft.com/en-us/azure/devops/repos/get-started/what-is-repos?view=azure-devops">What is Azure Repos?</a>.<br><br><strong>Azure Test Plans</strong><br>In this solution, you can run the tests on the browser and view the logs of the defects.<br>You can test your application no matter how and where it is, whether it is web, desktop, on-premise, cloud. The whole team can use the same testing process. For more information about Azure Test Plans, see <a href="https://docs.microsoft.com/en-us/azure/devops/test/overview?view=azure-devops">Overview of Azure Test Plans</a><br><br><strong>Azure Pipelines</strong><br>This is a place that we can call the heart of DevOps, namely Azure DevOps. Here, we can automate everything related to the software process (CI/CD process), so we can gain a significant advantage in time in compilation and deployment processes.<br><br>You can manage our build, test, deploy processes in any language from here,<br>If we want, we can run our application on both Linux and Windows machines in parallel,<br>We can deploy wherever we want (Azure, AWS, GCP or our own servers),<br>You can enjoy the benefits of containers,<br>We can make the application an image directly on Azure DevOps and push it to Docker Hub or Azure Container Registry.<br>We can do all these operations in the form of click-to-run from the shell or from the web, this gives us flexibility, we can follow the CI/CD processes or edit our codes from any device or even mobile.<br>In addition, it ensures that people who are not related to DevOps are included in these processes. All operations including the creation of Yaml (ie configuration files) can be performed via the web interface. For more information about Azure Pipelines, see <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/get-started/what-is-azure-pipelines?view=azure-devops">What is Azure Pipelines?</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d283907fa1d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>