multiwoven VS c4-notation

Multiwoven is now a leading Open Source Alternative to Hightouch, Census, and Rudderstack.

It's been a great journey so far, and we are excited to announce a major update to Multiwoven - our new release, Multiwoven 0.2.0, is now available!

Repo: https://github.com/Multiwoven/multiwoven

This release brings a host of new features, enhancements, and bug fixes to streamline data syncs and user experience.

From new connectors to advanced reporting dashboards, as a team, we have been working hard on these updates based on the feedback and requests from our customers and the community.

- 10+ new connectors added to Multiwoven, including

Repo: [https://github.com/Multiwoven/multiwoven]

Data movement has become a critical part of the modern data stack. more and more companies are evolving within the data movement space. The entire data movement landscape can be broken down into below product categories:

Data storage:

Congrats on the launch, I am building an OSS Reverse ETL project called Multiwoven (https://github.com/Multiwoven/multiwoven), built on top of many dev tools, frameworks etc. We manage to ship it using docker-compose to devs, wondering where does Flox fit in, can you help me understand with an use-case while docker exists?

(https://github.com/Multiwoven/multiwoven)

All the best & I'll watch your repo :)

Open Source No-Code data activation from Postgres to Airtable

https://github.com/Multiwoven/multiwoven

While the CDP market is growing rapidly, there is also too much noise and confusion around CDP vendors.

Today, most companies are unifying their customer data in a data warehouse. Data warehouses like Snowflake, BigQuery, Redshift, and others are becoming the single source of truth for companies and growing rapidly.

Naturally, companies want to make use of this data, and a CDP implementation becomes a natural choice.

But what companies fail to understand is that data control and ownership is a critical aspect of a CDP, companies tend to give away access to their datawarehouse to CDP vendors, which could lead to data privacy and security issues.

Today, open-source is growing rapidly, and companies are looking for open-source alternatives to every solution. Self-hosting and owning control of the data is a most preferred choice for companies.

That's exactly we are leading the charge with the first open-source warehouse native CDP.

Repo Link - https://github.com/Multiwoven/multiwoven

This is interesting, we are building https://github.com/Multiwoven/multiwoven an open-source ReverseETL and workflow orchestration is a big part of our platform, maybe I ca experiment with small use-case like setting up backend tests using flows.

The announcement just added more love to Ruby and the entire Rails community. When we started our oss journey, we were often questioned about why we chose Ruby and the suggestions to many other languages. https://github.com/Multiwoven/multiwoven

We are happy to see that Ruby is still the language of choice for many developers and companies. We can't wait to see what Ubicloud will bring to the Ruby community.

Second this.

Reference for anyone looking I to it: https://c4model.com/

There is also quite a lot of options for helping create these diagrams. I've found https://structurizr.com/ to be the best of what I've tried so far.

What you are describing sounds a lot like C4: https://c4model.com/

The C4 model [0] provides a mostly sensible structure and techniques for representing pure software systems across different abstraction levels.

For systems involving software and hardware, or other complex interfacing (both technology and bureaucracy) this starts to delve into the universe of systems engineering. There's a decent assembly of knowledge on that in the SEBoK [1].

As another commenter has already called out too, one of the most valuable sources of information is also _why_ a system is in its current form and _how_ that's changed over time. ADR's [2] really do a good job at nailing this for just about any scale.

[0]: https://c4model.com

[1]: https://sebokwiki.org

[2]: https://adr.github.io

There a various standards for documenting software architecture, like arc42 or C4. While useful and somewhat well-known (there is certainly a correlation here), here architecture documentation can be further simplified, particularly due to the self-similarity of project and component. Following is a small template, that can also serve as a project's and component's README:

I would suggest that if your architecture diagrams are a bunch of icons provided by AWS/Azure/GCP with lines pointing at each other... you are doing it wrong.

The 'what does this box do for my system' is vastly more important than the 'which in vogue offering from my cloud provider implements it'.

I highly suggest folks take a look at the C4 Model: https://c4model.com/

We often use abstractions in software engineering to communicate complex architectures and software systems. In this article, we’ll discuss how abstractions are inherently hierarchical and how the C4 model provides a nested structure for defining your software architecture. We’ll then cover how IcePanel allows you to create interactive and zoomable diagrams for your audience to zoom in and out of different levels of technical detail.

You probably want https://c4model.com/ which explains what a C4 architecture diagram is. (See the first footnote in the article.)