npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

temporalio-cluster-cdk

v0.4.1

Published

CDK constructs to setup a [Temporal](https://temporal.io/) cluster on ECS Fargate.

Downloads

12

Readme

CDK Constructs for Temporal cluster on AWS

CDK constructs to setup a Temporal cluster on ECS Fargate.

Note: this is currently a work in progress. At this point, I consider it as a proof-of-concept. However, I believe that, once completed, these constructs will provide a reasonable method for setup of production-grade application-scoped Temporal cluster in AWS/CDK environements.

Features

Current features

  • Setup a Temporal cluster on ECS Fargate
  • Use distinct containers for each Temporal server roles (frontend, history, matching, worker)
  • Specify the size of containers (can be specified specifically for each server role, or as default values)
  • Register frontend containers to a CloudMap namespace
  • By default, create an Aurora serverless (MySQL compatible) data store
  • Possibility of specifying Temporal software version, as well as modifying address of docker images (either to use a less restrictive docker registry, or to use customized build images)
  • Use an EFS file system to store and share Temporal's dynamic_config.yaml file among all server nodes
  • Automatically creates and upgrade the 'temporal' and 'visibility' schemas at launch time, if appropriate, without using the auto_setup container
  • Optionnaly launch the Temporal web UI

Missing features

  • Automatically create the default Temporal namespace at launch
  • Allow configuring distinct datastores for 'temporal' and 'visibility' schemas (notably, using ElasticSearch for 'visiblity')
  • Make it possible to easily configure the cluster as a single node cluster (that is, one container executing all roles). That would be useful for development in situations where the Temporal cluster is part of the application deployment
  • Configuration of auto-scalling
  • Propertly generate the configuration file
  • Register the Temporal web UI nodes to CloudMap
  • ...

Example usage

Note that default machine specs are intentionnaly small; also, in the following examples, removal policy is intentionnaly set to DESTROY. This is appropriate for tests and development purpose. In production, you should size up your containers appropriately and would most likely want to set removal policy to RETAIN (well, at least on your datastore).

Simple example

import { App, RemovalPolicy, Stack } from 'aws-cdk-lib';
import { TemporalCluster } from 'temporalio-cluster-cdk';
import { Vpc } from 'aws-cdk-lib/aws-ec2';
import { PrivateDnsNamespace } from 'aws-cdk-lib/aws-servicediscovery';

const app = new App();

const stack = new Stack(app, 'MyTemporalClusterStack', {
    region: process.env.CDK_DEFAULT_REGION,
    account: process.env.CDK_DEFAULT_ACCOUNT,
});

const vpc = new Vpc(stack, 'Vpc', {
    maxAzs: 2,
    natGateways: 1,
});

const cloudMapNamespace = new PrivateDnsNamespace(stack, 'CloudMapNamespace', {
    name: 'privatesvc',
    vpc: vpc,
});

const temporalCluster = new TemporalCluster(stack, 'TemporalCluster', {
    vpc,
    cloudMapRegistration: {
        namespace: cloudMapNamespace,
        serviceName: 'temporal',
    },
    removalPolicy: RemovalPolicy.DESTROY,
});

//
// temporalCluster.connections.allowDefaultPortFromAnyIpv4();
// temporalCluster.roleConnections.web.allowDefaultPortFromAnyIpv4();

app.synth();

Going farther

Specifying Temporal version

new TemporalCluster(stack, 'TemporalCluster', {
    ...
    temporalVersion: TemporalVersion.V1_14_1
    ...
}

Alternative or customized docker images

new TemporalCluster(stack, 'TemporalCluster', {
    ...
    temporalVersion: TemporalVersion.V1_14_3.withCustomizations({ repositoryBase: 'public.ecr.aws/123456789/' }),
    ...
}

Use an existing ECS cluster

const ecsCluster = new Cluster(stack, 'EcsCluster', {
    vpc: vpc,
    enableFargateCapacityProviders: true,
    containerInsights: true,
});

new TemporalCluster(stack, 'TemporalCluster', {
    ...
    ecsCluster
    ...
}

Taking control of the datastore

const datastore = new AuroraServerlessTemporalDatastore(stack, 'Datastore', {
    engine: DatabaseClusterEngine.auroraMysql({ version: AuroraMysqlEngineVersion.VER_2_10_1 }),
    vpc,
    removalPolicy: RemovalPolicy.DESTROY,
});

new TemporalCluster(stack, 'TemporalCluster', {
    ...
    datastore,
    ...
}

License

The MIT License

Copyright (c) 2022 Progymedia Inc. All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.