0% found this document useful (0 votes)
3 views3 pages

Python +

The document outlines a web application architecture integrating .NET Core, Angular, PostgreSQL, and Python on AWS. It describes various integration patterns for using Python with .NET Core, including Lambda functions, file uploads to S3, and ETL processes via AWS Glue. Additionally, it covers data sharing methods, authentication strategies, deployment options, and monitoring practices.

Uploaded by

Harsh Mendapara
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3 views3 pages

Python +

The document outlines a web application architecture integrating .NET Core, Angular, PostgreSQL, and Python on AWS. It describes various integration patterns for using Python with .NET Core, including Lambda functions, file uploads to S3, and ETL processes via AWS Glue. Additionally, it covers data sharing methods, authentication strategies, deployment options, and monitoring practices.

Uploaded by

Harsh Mendapara
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

🔄 Real-Time Project Notes: Python + .

NET Core + AWS Integration

✅ Use Case:

Scenario: A web application built using .NET Core (API), Angular (Frontend), PostgreSQL (DB), Python (for
ML or ETL logic), and AWS for cloud services.

🔹 1. Architecture Overview

[Angular Frontend] ⇄ [.NET Core Web API] ⇄ [PostgreSQL / AWS Services]


⇄ [Python Services via Lambda or Container]

🔹 2. When to Use Python with .NET Core?

• When your ML/AI/ETL logic is in Python.


• Python scripts as AWS Lambda functions for background tasks.
• Data preprocessing or analytics using Python (pandas, NumPy).

🔹 3. Integration Pattern 1: .NET Calls Python via Lambda

• Python script deployed as Lambda function.


• .NET Core calls it via HttpClient or AWS SDK.

var lambdaClient = new AmazonLambdaClient();


var request = new InvokeRequest
{
FunctionName = "MyPythonLambda",
Payload = JsonConvert.SerializeObject(new { userId = 123 })
};
var response = await lambdaClient.InvokeAsync(request);

Python Lambda:

def lambda_handler(event, context):


user_id = event['userId']
# do processing
return {'statusCode': 200, 'body': f'Processed user {user_id}'}

1
🔹 4. Integration Pattern 2: File Upload → S3 → Python Process → Notify .NET

• Angular uploads file → .NET Core API stores to S3


• S3 triggers Lambda (Python) to process the file
• Python publishes result to SNS or stores in S3
• .NET Core listens to result (polling or via SQS)

🔹 5. Integration Pattern 3: Python as ETL via Glue + Trigger from .NET

• Python ETL jobs defined in AWS Glue


• .NET Core triggers Glue job:

var glueClient = new AmazonGlueClient();


await glueClient.StartJobRunAsync(new StartJobRunRequest
{
JobName = "my-python-etl"
});

🔹 6. Common Data Sharing Methods

• S3 bucket (upload file/data → processed by Python)


• SQS queues (for async JSON messages)
• RDS/PostgreSQL (shared access from both languages)
• AWS EventBridge (advanced event-driven workflows)

🔹 7. Authentication and Secrets Sharing

• Use AWS Secrets Manager for DB/API keys


• Use IAM roles with minimum privilege
• JWT token flow can be fully handled by .NET Core

🔹 8. Deployment Strategy

• .NET Core: ECS Fargate / Lambda + API Gateway


• Angular: S3 + CloudFront
• Python: Lambda functions / ECS containers / Glue scripts
• PostgreSQL: Amazon RDS

2
🔹 9. Monitoring & Logging

• Use CloudWatch Logs for both .NET and Python Lambda


• .NET → Serilog AWS sink
• Python → boto3.client('logs')

Let me know if you'd like a real project repo example using this setup or a PDF version of this document.

You might also like