Apache Camel
terraform-cdk
Apache Camel | terraform-cdk | |
---|---|---|
21 | 104 | |
5,331 | 4,740 | |
1.0% | 0.9% | |
10.0 | 9.8 | |
1 day ago | 4 days ago | |
Java | TypeScript | |
Apache License 2.0 | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Apache Camel
- Show HN: Winglang β a new Cloud-Oriented programming language
-
Ask HN: What is the correct way to deal with pipelines?
"correct" is a value judgement that depends on lots of different things. Only you can decide which tool is correct. Here are some ideas:
- https://camel.apache.org/
- https://www.windmill.dev/
- https://github.com/huginn/huginn
Your idea about a queue (in redis, or postgres, or sqlite, etc) is also totally valid. These off-the-shelf tools I listed probably wouldn't give you a huge advantage IMO.
-
Is there something like airflow but written in Scala/Java?
Apache Camel Apache Nifi Spring Cloud
-
Why messaging is much better than REST for inter-microservice communications
This reminds me more of Apache Camel[0] than other things it's being compared to.
> The process initiator puts a message on a queue, and another processor picks that up (probably on a different service, on a different host, and in different code base) - does some processing, and puts its (intermediate) result on another queue
This is almost exactly the definition of message routing (ie: Camel).
I'm a bit doubtful about the pitch because the solution is presented as enabling you to maintain synchronous style programming while achieving benefits of async processing. This just isn't true, these are fundamental tradeoffs. If you need a synchronous answer back then no amount of queuing, routing, prioritisation, etc etc will save you when the fundamental resource providing that is unavailable, and the ultimate outcome that your synchronous client now hangs indefinitely waiting for a reply message instead of erroring hard and fast is not desirable at all. If you go into this ad hoc, and build in a leaky abstraction that asynchronous things are are actually synchronous and vice versa, before you know it you are going to have unstable behaviour or even worse, deadlocks all over your system and the worst part - the true state of the system is now hidden in which messages are pending in transient message queues everywhere.
What really matters here is to fundamentally design things from the start with patterns that allow you to be very explicit about what needs to be synchronous vs async (building on principles of idempotency, immutability, coherence, to maximise the cases where async is the answer).
The notion of Apache Camel is to make all these decisions a first class elements of your framework and then to extract out the routing layer as a dedicated construct. The fact it generalises beyond message queues (treating literally anything that can provide a piece of data as a message provider) is a bonus.
[0] https://camel.apache.org/
-
Can I continuously write to a CSV file with a python script while a Java application is continuously reading from it?
Since you're writing a Java app to consume this, I highly recommend Apache Camel to do the consuming of messages for it. You can trivially aim it at file systems, message queues, databases, web services and all manner of other sources to grab your data for you, and you can change your mind about what that source is, without having to rewrite most of your client code.
-
S3 to S3 transform
For a simple sequential Pipeline, my goto would be Apache Camel. As soon as you want complexity its either Apache Nifi or a micro service architecture.
-
ποΈ We have just released our JBang! catalog ποΈ
πͺ Apache Camel : Camel JBang, A JBang-based Camel app for easily running Camel routes.
- 7GUIs of Java/Object Oriented Design?
-
System Design: Enterprise Service Bus (ESB)
Apache Camel
-
Advanced: Java, JVM and general knowledge
So, my advice is this. Expand your knowledge. Pursue higher education on topics you are familiar with, but also explore topics you are not. Read documentation, but question it. I just found out about something called Apache Camel today that I am excited to read up on. Why is it better than Spring? Is it really? What's happening here? This is always what excites me as a developer and engineer. There is so much to learn.
terraform-cdk
-
Learning Go by examples: part 12 - Deploy Go apps in Go with CDK for Terraform (CDKTF)
At first I tested it to deploy an OVHcloud Managed Kubernetes Service (MKS) with a Node Pool. And step by step, it worked. I even created a Pull Request (PR) in the terraform-cdk repository to add it as an example βΊοΈ.
-
AWS CDK For Noobs: Deploying NextJS Apps
I'll be trying more sample app deployments with CDK and maybe even explore CDK for Terraform.
-
Show HN: Winglang β a new Cloud-Oriented programming language
You can use CDK with other providers using https://github.com/hashicorp/terraform-cdk
In my experience, CDK is far better than Pulumi, especially if you're mostly going to be using AWS.
- Terraform CDK
-
Why is Kubernetes adoption so hard?
I, personally, prefer Crossplane Composite Functions on top of CDK8S, but had dropped CDKTF due to bloat. You can actually manage Kubernetes updates/upgrade lifecycle with Crossplane, as well.
- Cloud, Why So Difficult?
- What are some harsh truths that r/devops needs to hear?
-
Backend engineers that don't like JavaScript
I was going to recommend Pulumi, but looks like CDK for Terraform is still being kept up to date.
-
Should i migrate from Kustomize to Helm?
Avoid Pulumi, get directly to source and use https://github.com/hashicorp/terraform-cdk
- AWS IAM Roles, a tale of unnecessary complexity
What are some alternatives?
Airflow - Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages π
Apache Kafka - Mirror of Apache Kafka
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
Apache Pulsar - Apache Pulsar - distributed pub-sub messaging system
crossplane - The Cloud Native Control Plane
Apache ActiveMQ Artemis - Mirror of Apache ActiveMQ Artemis
copilot-cli - The AWS Copilot CLI is a tool for developers to build, release and operate production ready containerized applications on AWS App Runner or Amazon ECS on AWS Fargate.
Spring Boot - Spring Boot
cdk8s - Define Kubernetes native apps and abstractions using object-oriented programming
Aeron - Efficient reliable UDP unicast, UDP multicast, and IPC message transport
aws-cdk-local - Thin wrapper script for using the AWS CDK CLI with LocalStack