Skip to main content

Posts

Understanding Microservices: What They Are and How They Differ from Traditional Services and APIs

  Understanding Microservices: What They Are and How They Differ from Traditional Services and APIs In recent years, microservices have become one of the most popular architectural styles for building modern applications. But what exactly are they, and how do they differ from traditional services or APIs? In this blog, we’ll break down what microservices are, their key features, and how they differ from the more traditional service-oriented architectures (SOA) or simple APIs. What Are Microservices? In the simplest terms, a microservice is a way of designing software as a collection of small, independent services that each handle a specific task or business function. Imagine you're building an online shopping application. Rather than having a massive, monolithic (one big block of) application that handles everything—user management, product catalog, payment processing, etc.—you can break it down into smaller services. For example: User Service : Manages user accounts, login...
Recent posts

Working with OAuth Tokens in .NET Framework 4.8

  Working with OAuth Tokens in .NET Framework 4.8 OAuth (Open Authorization) is a widely used protocol for token-based authentication and authorization. If you're working with .NET Framework 4.8 and need to integrate OAuth authentication, this guide will walk you through the process of obtaining and using an OAuth token to make secure API requests. Step 1: Understanding OAuth Flow OAuth 2.0 typically follows these steps: The client requests authorization from the OAuth provider. The user grants permission. The client receives an authorization code. The client exchanges the code for an access token. The client uses the token to access protected resources. Depending on your use case, you may be implementing: Authorization Code Flow (for web applications) Client Credentials Flow (for machine-to-machine communication) Step 2: Install Required Packages For handling HTTP requests, install Microsoft.AspNet.WebApi.Client via NuGet: powershell Copy Edit Install-Package Microsoft.AspNet.W...

The Evolution of .NET: From Framework to Core and Beyond

  The Evolution of .NET: From Framework to Core and Beyond The .NET ecosystem has come a long way since its inception, and perhaps one of the most significant transitions in its history is the shift from .NET Framework to .NET Core , which has since evolved into simply .NET starting with version 5. This transformation represents a major step in making .NET more modern, agile, and ready for the future, with a focus on cross-platform development, performance, and cloud readiness. In this blog, we’ll explore the key changes and advantages of the move from .NET Framework to .NET Core, and why it matters to developers. A New Era of Cross-Platform Development One of the most important changes in the transition from .NET Framework to .NET Core (and now .NET 5 and beyond) is the introduction of cross-platform support . .NET Framework: Windows-Only Historically, .NET Framework was tied closely to Windows, making it difficult for developers who wanted to build cross-platform applicat...

Understanding JWT and Its Implementation in .NET

  Understanding JWT and Its Implementation in .NET Introduction In modern applications, secure and efficient communication between client and server is essential. JSON Web Token (JWT) has become a popular standard for authenticating and authorizing users. In this blog post, we will explore JWT, understand its structure, and implement it in a .NET application. What is JWT? JWT stands for JSON Web Token , a compact and self-contained method for securely transmitting information between parties as a JSON object. It is widely used in stateless authentication mechanisms in web applications. Key Features: Compact : Suitable for URLs, cookies, and HTTP headers. Self-contained : Contains all necessary information about the user (e.g., claims). Secure : Uses cryptographic signatures to verify authenticity. Structure of a JWT A JWT consists of three parts: Header : Contains the token type ( JWT ) and hashing algorithm (e.g., HS256 ). Payload : Contains claims such as user information and me...

Querying Flow Instances and API Hits Data in Oracle SOADB: Handling Lock-Free Reads

In Oracle SOA Suite , runtime metadata for composite applications, flow instances, and API hits is stored in the SOA Infrastructure Database ( SOADB ). SQL Server users often use NOLOCK to avoid locking rows during queries, but in Oracle, the multi-version concurrency control (MVCC) model inherently prevents readers from blocking writers. However, there are Oracle-specific methods to emulate lock-free or low-lock reads when querying SOADB. This blog will guide you through querying flow instances and API hits data from SOADB and explain how to ensure lock-free behavior. 1. Key Tables in SOADB for Flow Instances and API Hits Flow Instance Data COMPOSITE_INSTANCE : Stores composite-level instance information, such as state, creation time, and last modified time. CUBE_INSTANCE : Provides details about BPEL process-level execution. MEDIATOR_INSTANCE : Contains information about Mediator flows within composite applications. API Hit Data DLV_MESSAGE : Tracks delivery messages, including...

Managing and Updating SSIS Jobs and Data in SQL Server

Managing SQL Server Integration Services (SSIS) jobs and their configurations often involves interacting with SQL Server Agent ( msdb ) or the Integration Services Catalog ( SSISDB ). This blog will guide you through accessing, understanding, and updating SSIS-related data step-by-step, with formal design considerations for robust, production-ready implementations. 1. Understanding SSIS Jobs and Data Storage Before diving into T-SQL queries, it’s crucial to understand where SSIS-related data is stored: msdb : Stores SQL Server Agent job details, including schedules and job steps. SSIS jobs are typically defined here as Agent job steps that invoke SSIS packages. SSISDB : Stores deployed SSIS packages and execution metadata. It is introduced in SQL Server 2012 as the Integration Services Catalog. Each database serves different purposes: msdb helps manage job scheduling and orchestration. SSISDB allows for detailed control of SSIS packages, including parameters and execution history. ...