IZ Analyzer, a dynamic code analysis tool, has garnered significant praise from a diverse range of clients, each with their own unique perspectives on what makes it stand out. Client Feedback: A Deep Dive Client from a Fortune 500 beverage manufacturing: Specialized MuleSoft Code Scanning For this global leader in the beverage industry, the specialization …
Continue reading “Customer Success Stories: Why IZ Analyzer Is a Game Changer”
One of the most frequently asked questions is if we have static code analysis and a well defined DevOps process, why would we need run time code analysis? In this article, let’s explore the differences between the two and why you might want to have runtime code analysis (and IZ Runtime Analyzer) even if you have …
Continue reading “MuleSoft Runtime Code Scanning – Why Do You Need It?”
As software development becomes increasingly complex and the demand for high-quality software grows, it is essential for developers to adopt tools and practices that help them create better code. Static code analysis is one such tool that has gained popularity in recent years. Static code analysis is a process of analyzing code without actually executing …
Continue reading “Static Code Analysis: 10 Ways It Saves You Time, Money, and Headaches”
👨💻 Over the past two years, IZ Analyzer has established itself as the undisputed market leader in MuleSoft static code analysis. But we’re not stopping there – we’re excited to announce the upcoming release of our Runtime Analyzer feature, taking code analysis to the next level. 🔝 👀 Our research has revealed a ticking time …
In the API driven integration ecosystem, Mulesoft™ is an industry leader. MuleSoft’s Anypoint Studio and Anypoint Platform offer rapid development speed, resulting in easy, fast, and scalable API development. It is indeed enterprising and more and more clients are leveraging MuleSoft for their iPass solutioning. With the speed of API development that MuleSoft offers, the …
Continue reading “MuleSoft Automated Code Quality Review – Why IZ Analyzer?”
Mulesoft development fundamentals is a blog series that takes you through various aspects of Mulesoft development from “how to structure your Mule code” to “Things to cater to when you deploy to production”. This is an attempt to share the expertise that we have gained after working with several Mulesoft enterprise clients. This read will …
Continue reading “Mulesoft Development Fundamentals: Mule Project Structure”
Overview Anypoint Platform configuration is a key challenge for any MuleSoft Solution Architect. Any client, small or large, would have multiple lines of Business or Business Units. They might be grouped within centralized or decentralized teams or even run single or multiple projects at any given time. MuleSoft has the concept of Business Groups. These …
Continue reading “Mulesoft: Anypoint Platform Business Group Limit”
GraphQL benefits and whether it trumps API or works alongside it is a discussion for another blog post. This blog post takes a very quick walk-through of the GraphQL router from MuleSoft – aimed at developers to quickly get things up and running and try it out for themselves. Step 1: Install GraphQL Router GraphQL …
Code coverage is a metric that can be used to check the percentage of source code that has been tested using test cases. In this blog we will be discussing about generating and uploading Mule Munit coverage reports to IZ Analyzer. Overview IZ Analyzer aims to improve the quality of your Mule source code using …
In this Vlog, we introduce you to IZ Accelerators, a product that adds value in the Design stage of your C4E lifecycle.
In this vlog, we explain how IZ Ops helps achieve DevSecOps with automated deployments to Anypoint Platform, insight into deployment statistics, property management across multiple environments, access control, and auditing.
In this video, we explain how Automated Code Quality Review can be achieved with the help of IZ Analyzer. We demonstrate Anypoint Studio plugin that helps review the code based on pre-defined set of rules in real-time.
In this read, I have attempted to highlight basic features that should be present in every System API. A poorly designed System API will always need enhancements or other process/experience APIs built on top of it, to get the best out of it.
