Apache Camel
wing
Apache Camel | wing | |
---|---|---|
21 | 51 | |
5,331 | 4,557 | |
1.0% | 19.9% | |
10.0 | 9.9 | |
1 day ago | 5 days ago | |
Java | TypeScript | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
wing
-
Inflight Magazine no. 9
Cloudflare
-
I fine-tuned my model on a new programming language. You can do it too! π
In Winglang, we wanted to use OpenAI and ChatGPT-4 to answer people's questions based on our documentation.
-
7 Programming Languages Every Cloud Engineer Should Know in 2024!
Wing's design philosophy emphasizes productivity, security, and efficiency, enabling developers to stay within a single, intuitive workflow throughout the development process.
-
Developer's Toolkit: Your Essential Open Source DevTools
Please star β Wing
-
Crafting Custom Platforms in a Cloudy World βοΈ
Click the picture to star β Wing
-
Cloud, why so difficult? π€·ββοΈ
Check out https://github.com/winglang/wing for more details.
-
π 9 Top Trending Open Source Projects to Watch for in 2024
1. Wing
-
10 Ways for Kubernetes Declarative Configuration Management
Winglang - Winglang is a new cloud-oriented programming language that combines infrastructure and runtime code in one language, supporting multiple build targets such as AWS and Kubernetes. Additionally, Winglang provides built-in libraries for direct manipulation of containers and Helm Chart configurations.
- Winglang - New Cloud-Oriented Programming Language
-
Winglang: New open-source programming language for faster and simpler cloud development
A group of dedicated contributors and myself are working on Winglang, a new programming language that reduces complexity and speeds up cloud development by allowing developers to work at a higher level of abstraction and test their applications locally with a fully functional simulator that provides instant feedback after code changes.
What are some alternatives?
Airflow - Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
Apache Kafka - Mirror of Apache Kafka
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
Apache Pulsar - Apache Pulsar - distributed pub-sub messaging system
nballerina - Ballerina compiler that generates native executables.
Apache ActiveMQ Artemis - Mirror of Apache ActiveMQ Artemis
eventual - Build scalable and durable micro-services with APIs, Messaging and Workflows
Spring Boot - Spring Boot
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages π
Aeron - Efficient reliable UDP unicast, UDP multicast, and IPC message transport
vscode-infracost - See cost estimates for Terraform right in your editorπ°π