System Architecture

Good to know: Outlining how updates work will help everyone know how they collaborate with the system, having a robust approach to updating our design system is super important – afterall a design system is never complete!

Here's a few walkthroughs on how our different tools align and work

• We use Cloudformation AWS infra using Infrastructure as code (IaC) [yaml] ✅

With Cloudformation we can Automate, test, and deploy infrastructure templates with continuous integration and delivery (CI/CD) automations

• AWS Elastic Load Balancing ✅

Elastic Load Balancing (ELB) automatically distributes incoming application traffic across multiple targets and virtual appliances in one or more Availability Zones

• AWS Health Checks ✅

• Cloudflare Health Checks ✅

The load balancer sends a health check request to each registered instance every Interval seconds, using the specified port, protocol, and path.

• Amazon CloudWatch alarm ( manually)

A metric alarm watches a single CloudWatch metric or the result of a math expression based on CloudWatch metrics.

A composite alarm that includes a rule expression that takes into account the alarm states of other alarms that we have created. A composite might go into ALARM state only when all of the underlying metric alarms are in ALARM state.

We can monitor and receive alerts about our AWS resources and applications across multiple regions. After we add an alarm, the alarm turns gray when it's in the INSUFFICIENT_DATA state and red when it's in the ALARM state.

Jenkins additionally added:

JenkinsDevOps

FYI the current machine is small so might cannot handle the current connections

To add:

NetData

--> https://github.com/netdata/netdata

--> https://app.netdata.cloud/