The quickest way to check your Mulesoft code quality is here. Built on the robust IZ Analyzer engine, this tool automatically scans your Mule project for over 180+ industry standard rules. We made this short video to illustrate how you can quality check your Mule projects absolutely free. Happy Analyzing! Try our Online Scanner now: …
Creating a Custom Rule is one of the most exciting features of our Code Analysis Product, IZ Analyzer. Better yet, all it takes is a few lines of simple groovy script! This short video shows how to create, define and execute your first custom rule in IZ Analyzer. Give it a free try here: https://analyzer.integralzone.com/try
PostgreSQL relies on replication for high availability, failover, and balancing read requests across multiple nodes. Streaming Replication ensures that data written to the primary PostgreSQL database is mirrored on to one or more standby (replica) nodes. Standby nodes accept read-only connections, so all traffic related to any Reporting or BI Dashboard applications can be routed …
Continue reading “Kubernetes – Configure PostgreSQL Streaming Replication”
In this Vlog, we introduce you to IZ Accelerators, a product that adds value in the Design stage of your C4E lifecycle.
Through these videos, we aim to provide insight into products and tools that have significantly contributed to accelerating C4E Adoption at reduced costs and increased efficiency.
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.
REST has been ruling the API industry for a long while now. One of all the reasons why REST has been so successful is that REST is highly optimized for servers.
But for a long time, we have been focussing on creating APIs which are highly optimized for servers and not clients. GraphQL lets you build APIs which are more client-centric than ever.
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.
Okta is chosen as external client management to create dynamic client applications and grant, authorize and introspects tokens using Okta. The role of Okta includes creation of Client Id and Client Secret, as well support for OAuth flows – Authorization code and client credential.
Out of all the concepts, best practices, and principles that are talked about an API and its design, the one that usually given the lesser importance is an API error response. A part reason for this shortcoming is that everyone is happy till the time API is working fine. So lets put little thought into how should we treat the failure of an API function.
Learn to develop SOAP Web Services using Mule, deploy it on Anypoint Runtime Manager and manage the deployed Web Services using Anypoint API Manager by applying policies.
Visualize your application network using Anypoint Visualizer. Explanation with System APIs, Process APIs and Experience APIs
