This template is brought to you by Lucidchart, a diagramming app for Confluence.
...
Diagram owner
...
Team
...
Informed
...
Status
...
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
...
Last date updated
...
...
On this page
...
| Table of Contents | ||||
|---|---|---|---|---|
|
...
| title | Pillars of the AWS Well-Architected Framework |
|---|
...
Name
...
Description
...
Operational Excellence
...
The ability to run and monitor systems to deliver business value and to continually improve supporting processes and procedures.
...
Security
...
The ability to protect information, systems, and assets while delivering business value through risk assessments and mitigation strategies.
...
Reliability
...
The ability of a system to recover from infrastructure or service disruptions, dynamically acquire computing resources to meet demand, and mitigate disruptions such as misconfigurations or transient network issues.
...
Performance Efficiency
...
The ability to use computing resources efficiently to meet system requirements, and to maintain that efficiency as demand changes and technologies evolve
...
Cost Optimization
...
The ability to run systems to deliver business value at the lowest price point.
AWS Well Architected Framework PDF
Goals
📐 Architecture
<Add diagram>
Install your favorite diagramming app from our Marketplace, then use the / command to embed an architecture diagram in this table. Try using the Lucidchart AWS diagram.
Architecture flow
Other notes:
🚀 Deployment strategy
Deployment region:
⌨ Rest API details
| Code Block |
|---|
{
"samplecode: string"
} |
🤝 SLA
Requests Per Second (RPS):
Latency:
Goals
Self-hosted Managed Connector that will be used by multiple users for hosting their own connector
Chain of thoughts during discussion
Self-hosted participant software installer →. generates UI → goes to server → fires up connectors → run connectors → data exchange through CSV files
One server (EC2 instance) used for multiple connectors hosted for multiple/single users
Test the capacity of instance and configuration for a limit on connectors that could be hosted
Experiment on possibilities and limitations of this idea
Take 4 GB of RAM and observe number of connectors
Technologies to be used:
Docker containers with or without Kubernetes
[ OR ]
Kubernetes only
Limit of connectors per user
Have to decide on a number?
Server (EC2 instance) will be destroyed after all connectors running inside are stopped
Should be automated
Multi-threaded creation of connectors
How should it be managed?
Technology?
System Design?
Database can be anywhere
Need more info?
Timeline of each connector
Destroy the connector after it’s time is over
Expanding capacity using Lambda
Need more info?
Celery worker to observe/ manage visualization
Finalize on class of machines for AWS instance
Working Pieces Readily Available
setup.py that does all of the above (however, have to experiment for scalablity) (link)
Loom video by sagar (link)
Video by Waseem (link)
✅ Action Items
Action | Description | Owner | Due date | Jira ticket | |
|---|---|---|---|---|---|
| 1 |
| ||||
| 2 |
| ||||
| 3 |
|