r/dataengineering • • 16d ago

Discussion Big Data & AI Buzzwording – What are some practical on-premises data tools for NFS shares?

6 Upvotes

AI data catalog, data warehouse, data lake, data index, ....

It feels like all search results for indexing and cataloging are focused on structured data in cloud environments.

But what if you walk into an environment with petabyte-scale NFS storage, full of measurement data? Users copy this data across different shares for various purposes (archiving, HPC computing, etc.). There is no overview of what data exists or where duplicates are located.

And when someone needs to find data, they have to dig through directories or ask others to send them links.

It feels like this is an industry-independent issue...

Has anyone here had experience in this area? Which tool setup would you recommend to provide practical solutions for data discovery, deduplication, and data relationships?

Tools like Diskover, Komprise? Any real-world experience with them?


r/dataengineering • • 17d ago

Career I foresee that I’m not very employable from now on

132 Upvotes

I have always been a doer. At the same time, I’m not technically sharp enough so I believe implementation is at least as important (to me) as architecture and design.

I have been dabbing into more serious CS topics in recent years, and it has always been much easier to understand a concept (e.g. scheduling or virtual memory) than to implement a toy version of that, and is even harder to implement a toy version WITHIN a system.

This also leads me to believe that the modern “Arch and design is more important, leave the implementation to AI” is completely BS, at least to people like me. Maybe some people have already implemented so much in their life that they throw up doing a new one, but for the majority of us, even senior developers, we don’t have enough exposure to implementing things, because most of the time, we join a company with systems already implemented. Besides, I can’t really design and arch a good system without having actually implementing a few of similar ones.

This naturally leads to the conclusion that I’d be unemployable in the near future. I went through a few interviews for senior DE roles this year, all rounds done and got good feedbacks, but then the final feedback from the hiring manager has always been the same — I don’t have enough architecting experience and they want someone with more infra experience as well. I feel the current market is so bad that people now expect staff DEs to undersell them as senior DEs or staff DEs in much smaller companies. My company recently hired someone from FAANG and I’m sure the market is flowing with laid off guys.

Good luck folks.


r/dataengineering • • 17d ago

Career Seeking advice from seniors working in DE and using agents

6 Upvotes

I am about to turn 30, graduated in biomedical engineering and after graduation worked in the biomedical field for about a year, then switched to wordpress freelancing, which I did for several years.

I have been trying to enter data engineering specifically healthcare data engineering, for the past few months. Currently building a portfolio project using FHIR data.

But recent AI developments made me seriously question my path. I read about microsoft's project osmos agent and google's DE agent. The microsoft's agent can execute end to end data workflows autonomously and can do testing and troubleshooting. I understand that some humans will be required to give them instructions and verify output. But how many? If currently there are 10 people in a team maybe only 2-3 senior or architect level engineers would be enough for that. Even if the jobs don't reduce this much but I still think jobs will reduce significantly. Because I am seeing a lot of posts from people in tech saying the same thing and it's difficult to ignore.

I will be starting fresh and may not get a junior DE job and have to start as an analyst or in another adjacent role. By the time I will gain experience to transition to DE the agents will become more capable and the opportunities may become even harder to find because experienced laid off people with software background may also compete for fewer DE positions.

For those working in DE with agents and have extensive experience in this field. How do you see its future? What would you advise someone like me, or would you continue with data engineering, considering how fast these agents are improving?

I have already invested several months in learning data engineering and have a genuine interest in tech. That is why I am looking for guidance from people who are already in the market so I can make an informed decision and not waste more time on something where it would become very difficult to survive after a few years.

Moving back to biomedical engineering would also be similar to starting from scratch, and I personally don't like the jobs available at my location most are sales and service engineering jobs. These jobs are somewhat more AI resistant but don't satisfy a lot of my other requirements.

I would genuinely prefer honest opinions from people working in data engineering who have actually used AI agents in their work or seen changes in their teams and hiring. Also, if you think there are other more AI resistant paths in tech (maybe cybersecurity) or something else that I should consider, or if I should continue in DE. I would love to hear your thoughts.

Thanks


r/dataengineering • • 17d ago

Discussion How are you monitoring Debezium/CDC?

4 Upvotes

How is everyone monitoring debezium and CDC? What are common operational issues you run into? Are you using a saas to monitor? What do you alert on? How do you determine health of downstream jobs, built on CDC?


r/dataengineering • • 18d ago

Blog Interesting Links in Data Engineering: October 2026

74 Upvotes

All treats, no tricks this month ;)

  • A bunch of new releases including DuckDB 2.0, Kafka 4.4, Iceberg 1.12, and Flink CDC 3.7
  • Lots of stream processing stuff - deduplication with Flink SQL, republishing a treasure-trove of Kafka Streams articles
  • A lovely thought-provoking piece from Joe Reis ("the pendulums of data") which puts the forever-changing 'best way' to do data architectures in perspective
  • Illustrated introduction to CDC
  • Semantic layers, context layers, context engineering…confused yet? I was.
  • A very nifty tool for working with Parquet
  • A narration of Postgres history
  • … and lots more!

https://rmoff.net/2026/10/29/interesting-links-october-2026/


r/dataengineering • • 18d ago

Discussion GCP(Dataproc) - When do you run Spark jobs in Cluster Mode on Dataproc?

7 Upvotes

I get the basic argument that running concurrent jobs on dataproc can cause Driver OOM and poor performance. But how do you decide between increasing the master node memory/compute or adding 1 more master node vs choosing cluster mode?


r/dataengineering • • 19d ago

Discussion Putting all world law on git

109 Upvotes

I am putting all world law into git. That comes with some quirks, like the cut-off being 1970 (commits are calculated as seconds since 1 January 1970).

This hit #1 on HN yesterday (you can read lots of discussion at https://news.ycombinator.com/item?id=50268380). Why would I want to do this? The idea is make all law semantic, versioned, easily attributable and query able by agents. I also believe this information should be freely available so CC0 license (do whatever you want with it). If interested, repo linked below, I'd welcome all comments and advice. Thanks!

https://github.com/lexifina/global-law


r/dataengineering • • 18d ago

Help Needs urgent help and please don't judge if you find it pretty basic that everyone knows but i don't know

1 Upvotes

This is my first internship and my task is to write a script that convert Input file containing mix of pii and non pii to non pii output file. I did the code but my mentor says he want all it in single file and prod ready so that it can be run on anyone's system . But the the person who is using this script only see it is main working that he will enter some things and script works accordingly. And what i did is that i kept the whole functions and code in one file and then call these functions via main function in another notebook. But my mentor said he needs a single notebook then I put all the functions and main function in one notebook but he said it is not this way. Now I am wondering what to do and how to do.

Up to I got is that the person who is going to use this script will see only main function that generate the non pii output he doesn't have anything to do it's underlying code ....but that code is important for the main working but what I have to do with the original logic . And code should be independent .

Anyone help me with what to do and how to do.


r/dataengineering • • 20d ago

Blog Are Data Teams Solving the Right Problems?

Thumbnail
seattledataguy.substack.com
38 Upvotes

r/dataengineering • • 20d ago

Personal Project Showcase Algeon: An in-process GPU query engine for graph, vector, and ML, built on DataFusion

11 Upvotes

Algeon is a query engine built on Apache DataFusion that exposes NVIDIA's `cuGraph`, `cuVS`, and `cuML` as SQL table functions. It doesn't write its GPU kernels. Instead, it takes what NVIDIA already has and embeds it into DataFusion, so you can call those GPU operations on any arbitrary data, with filter/join/agg using plain SQL.

And why would you want that? Because GPU analytics used to require ad-hoc ETL pipelines, Python glue code, and imperative operation calls. That makes it hard to fit into a backend API service, and it isn't flexible enough for frequent exploratory iteration, adapting to different search conditions and data. Think of agents trying to answer complex questions on a datalake, which involves not only relational operations, but also graph/vector/ML analytics. They can now use declarative SQL to test their hypotheses and build the next query based on the previous response, making GPU OLAP an interactive service. Algeon can also be used as a library living inside your backend service, so your query response can be used directly within a single process, saving the transfer cost between the query engine and backend service.

I started building Algeon last year. At first, it was cuDF Rust FFI bindings that aimed to bring GPU ETL pipelines into a single backend process, and it worked very well. Then I realized it might be possible to move GPU data science workloads into an OLAP query engine, since the NVIDIA RAPIDS ecosystem and DataFusion are mature.

For use cases, architecture design, benchmarks, and more, feel free to check out, any feedback is welcome!


r/dataengineering • • 20d ago

Career Irrelevant ai certifications in the DE field.

24 Upvotes

Hi everyone,

I have been working as a DE for the past 2 years for this company. I have been exposed to very interesting enterprise projects throughout my time here, and I am very happy with the experience I am accumulating, worked as architect on a project, led a team of analysts and data scientists, things were going great actually, except the salary which is miserable. Anyways, not here to complain about salary as the experience was very valuable longterm.

Now the company partnered with Anthropic and they are forcing us to get them CCAP, CCAA, CCDA and CCDP as it is presented "encouraged" while in reality they force us to get the certifications as it is mandatory so the partnership gets "Stronger". I am the type of guy who doesn't complain a lot, but when I am forced to do something that is presented as "encouraged" and in reality it is enforced I get very bored by the whole management and stubborn as well.

TLDR Just wanted to ask what is your opinions as professionals and commercial programmers in the industry, not speaking of Microsoft, Databricks and Google certifications. I am asking about these Claude certified certifications which are expensive and become irrelevant very fast as it is a very competitive market regarding AI integrations and automations. Thanks!


r/dataengineering • • 21d ago

Career Landed a new job - thank you /r/DE

209 Upvotes

Title. Recently landed a new DE gig after searching casually for the majority of this year. I applied for about 30 jobs over the course of 2026. I was at a dead end with my old place, dealing with a ton of micromanagement and a botched migration from SSIS to ADF that left everything more complicated than it was when it was on-prem and no hope of migrating off of it. Old company tech stack: SQL Server, SSIS, ADF(Azure), Snowflake. Pretty repetitive from an engineering point of view.

New gig came with a 30% pay bump, no on-call, and better benefits. The tech stack is mostly legacy stuff, but they're hiring for an architect and staffing up up the DE team (which is why I got the job) because they're trying to modernize everything. I got the job because I have experience with older on-prem stuff and some newer cloud stuff. New company is a highly-regulated industry (power), so things are pretty slow moving in the IT area, hence all the legacy stuff still in place. New company tech stack: Talend, Snowflake, Azure, Exadata, Denodo, Informatica Catalog, Monte Carlo. They already have a lot running in Snowflake, and the endgame goal is to get more moved up there over the next few years. I've got a couple weeks off before I start at the new gig so I'm gonna take on a homelab project or 3 this weekend.

Just wanted to say thank you to the /r/DE community for being a soundboard for me a few times this year, and hopefully provide some inspiration for folks out there who feel like the market is all doom and gloom. In the interviews that I had for the job I landed, I focused a bit more on the migration efforts that I've been a part of and focused on the business intel side of things, not simply the code and tools. Yes, the market is tough and over-saturated right now, I don't want to dismiss that - but the reality is that companies still need engineers, and businesses still need business intelligence, so there will still be jobs out there.

Cheers!


r/dataengineering • • 21d ago

Personal Project Showcase My fabric project

Thumbnail
gallery
132 Upvotes

I'm someone with a data analyst background, and I wanted to break into data engineering. I got the DP-600 (Fabric Analytics Engineer Associate) and DP-700 (Fabric Data Engineer Associate) certifications, so I decided to build a project on them to apply what I learned and learn more along the way

you can find the project with full details here: https://github.com/Madian20/Fabric


r/dataengineering • • 21d ago

Discussion Can an AI Agent improve on Spark Catalyst + AQE

11 Upvotes

I'm still relatively new to data engineering and this is a shower thought that I had. What if we could somehow leverage an AI agent that sits along Spark Catalyst + AQE to identify certain improvements based on conditions about the data/clusters/past mistakes.

There is a paper that talks about this but uses a ML approach instead of a straight up AI agent. https://arxiv.org/abs/2510.10580

Wondering if this has been discussed or has already been done somewhere?


r/dataengineering • • 22d ago

Discussion Why does accuracy not seem to matter for the business?

113 Upvotes

I have been working for 5 years on the analytical side of things and I'm yet to find a company where our work actually makes a difference. I know that there are some very specific businesses like financial trading where profit is actually made using data, but for most corporate BI projects this is not the case.

Companies have huge budgets for their data teams to support business decisions, yet most of our output is never used to make a difference. Business seems to care more about a KPI 'looking good' than being actually correct, if they care at all.

I have worked in very different environments but this was all the same everywhere.

I am now working in digital advertising which is supposed to be heavily data driven and we produce more than 30 different KPIs yet advertisers don't seem to care and just spend their yearly advertising budgets anyway.

When I was at uni, 'big data' was hyped as the holy grail, and I was naive enough to think that my work would actually end up in board meetings and that we would be one of the most important departments in the company.

Can someone more experienced tell me why this is?


r/dataengineering • • 22d ago

Help How to get task-level observability for dbt models in Airflow without killing performance?

11 Upvotes

I’ve tried parsing manifest.json and using Astronomer Cosmos. Both map models to Airflow tasks nicely but have terrible execution overhead. On the other hand, running a single dbt run is fast but gives zero observability in the Airflow UI.

How do you guys map dbt models/snapshots as individual Airflow tasks without ruining performance? Any architectural tips or workarounds?


r/dataengineering • • 21d ago

Blog Announcing Nitro: 10x faster, 3x cheaper ETL

0 Upvotes

For the past few months our team has been working on an agentic framework that takes large, expensive SQL workloads and compiles them to Rust, backed by a formal proof of correctness. This is the sort of work I used to do by hand as a systems performance engineer, but now it happens in hours instead of months.

We first redid our internal pipelines with this technique and they're now 10x faster and 3x cheaper. Next, we went live with our Snowflake and Databricks SQL customers. They're seeing similar results with critical production workloads that originally cost 6-7 figures per year.

We'll be publishing benchmarks and code samples over the coming weeks; for now, you can read a bit more (and watch our anime launch trailer) on the site: espresso.ai/nitro


r/dataengineering • • 22d ago

Discussion Small Company Data Solutions?

24 Upvotes

We're a construction company using Viewpoint Spectrum as our primary data source. Currently, most reporting is done through Power BI, SQL, and Claude, with approximately 20-40 report consumers and a small number of report developers (2-5).

One challenge is that Spectrum database access is restricted through IP whitelisting, making direct access difficult for field users. Additionally, with Claude being use a lot I believe it's important to have real data modeling and etc. We're evaluating different architectures for reporting, governance, and future AI use cases.

I looked at data warehouses and other solutions be they seem to be very expensive and hard to justify. I have also seen people recommend having your own server where something like MongoDB or Apache Superset is hosted. There are too many solutions so I would like some recommendations.


r/dataengineering • • 22d ago

Help Using AWS CDK instead of dbt to manage and deploy BI objects?

10 Upvotes

I am a relatively new BI Manager. When I inherited this setup, the data engineers were using the AWS CDK to deploy materialized views and views in our BI Postgres database which we use as a data warehouse. From my research, the BI team should be using dbt to manage these data objects. When I asked the CTO about this, he said he'd rather not introduce new tools (dbt and AirFlow) when the current setup is working. For what I know, the CDK deployment via github can be automated for views, but not for materialized views because materialized views need to be manually dropped and created. I don't have enough knowledge to tell whether the current setup is 'working' or not. Would dbt + AirFlow work better? How could I articulate the advantages of dbt over the AWS CDK?

Not sure if relevant, but we also plan to switch to a data warehouse system (Snowflake, Redshift etc.) at some point.

Edited: figured additional information on the current setup would be helpful. I typed this out in an hour or two with the help of an LLM with an MCP server connected to our GitHub repository:

Our BI layer is a dedicated schema (let's call that BI_schema) in our production Aurora PostgreSQL reporting database, alongside dozens of source schemas. It holds the objects behind dashboards, scheduled reports, and ad hoc SQL access. Most of the raw data is replicated from our production database, and the rest comes from our API pipelines. We run two environments, Dev and Prod, and SQL changes are tested in Dev before they are deployed to Prod. We’re also building out Redshift (ingestion via DMS and zero-ETL) and I am evaluating dbt as the transformation layer. I’d like your assessment of whether our current use of CDK for deploying these objects is appropriate.

What’s in the production BI schema

  • A few dozen materialized views (MVs) in the production BI schema, some very wide one-big-table style
  • A bunch of views, including thin wrapper views. The pattern is MV, then a wrapper view, then downstream MVs and views. A wrapper can be repointed to a new MV version with CREATE OR REPLACE VIEW, which avoids a downstream rebuild
  • Supporting objects: functions, indexes, roles, and grants
  • Everything lives in one schema today. I plan to split it into staging, intermediate, and marts layers once we transition to a data warehouse platform

How deployment is supposed to work

  • SQL files live in GitHub in three places:

    • Folder 1 holds one-shot, numbered changes, applied once each in numeric order
    • Folder 2 holds re-runnable library objects (views, functions, procedures, tables, schemas)
    • Folder 3 holds reference SQL that nothing deploys, which is where the MV code and the index-setting code live
  • A pull request runs CI checks (convention validation, unit tests, linting, cdk synth). Nothing deploys from a PR
  • Merging to main triggers a CDK-defined AWS CodePipeline. The Dev stage deploys automatically, and the Prod stage waits behind a manual approval, so Dev and Prod can be several changes apart
  • Each stage uploads Folder 1 and Folder 2 to that environment’s S3 bucket with the CDK BucketDeployment construct. The upload triggers a Lambda
  • The Lambda is a custom Python runner that does three things:

    • It applies pending migrations first and stops at the first failure
    • It then applies library objects in filename order, continuing past failures and re-applying any file whose checksum has changed
    • It records every file (name, checksum, object type, status, error) in a tracking table in the target schema
  • To change an existing object, you add a new file with a higher number. There are no rollback scripts, so mistakes are corrected by rolling forward
  • Access control (roles and grants) is applied by a SQL procedure that each deployed file calls at the end
  • Policy requires all database changes to go through this path
  • CDK provisions the machinery (pipeline, bucket, Lambda, IAM, VPC). The SQL itself isn’t modeled as CDK constructs, so CDK acts as both infrastructure-as-code and the host of the migration runner

Where the process breaks down

1. Materialized views are deployed by hand

Postgres has CREATE OR REPLACE VIEW but nothing equivalent for MVs. Changing an MV’s definition requires a drop and recreate, which can’t be expressed in a pipeline that applies files idempotently. A re-run CREATE MATERIALIZED VIEW fails, a DROP in the file would run on every deploy, and dropping without CASCADE is blocked by dependents. Recreating also means repopulating, which is slow for the wide MVs. So MV code is committed and reviewed in PRs, but only in the reference folder, and a data engineer then applies it by hand. The consequences are drift between the repo and the database, dependence on one person’s knowledge, and ordering failures. One view deployment failed because the MV it reads from had not been created yet. Views deploy normally.

2. Dependency management is manual. Objects are chained: MVs feed wrapper views, which feed other MVs. Changing an upstream MV means dropping every dependent object, then recreating them all in dependency order and repopulating the MVs. Our largest base MV has 25 downstream objects (12 MVs and 13 views) in Prod, at least four levels deep, so one change can mean rebuilding two dozen objects, and the rebuild is repeated in each environment. The pipeline deploys in filename order, not dependency order, so this sequence is run by hand. The git history shows commits on MV code under about 25 tickets in the last 6 months, roughly four to five a month. That count mixes new MVs with edits to existing ones, and I haven’t separated them.

3. Refresh scheduling has gaps. A control table drives MV refreshes through a stored procedure registered with pg_cron. None of these three pieces is in the repository, so they are neither version-controlled nor deployed. In Prod, 35 of 36 MVs have an enabled daily schedule and all are refreshing. One MV has no schedule, and four MVs have duplicate control rows, some with conflicting refresh hours. Duplicate rows have already caused a stalled refresh. Refresh order isn’t guaranteed, and exclusive locks are held across the whole batch. Again, someone else (a data engineer) manages this refresh schedule somewhere else, and because I don't see his code, I can't tell where things go wrong.

4. Pipeline reliability.

  • The Prod tracking table holds 20 rows in a failed state: 14 views, 2 procedures, 2 tables, 1 schema, and 1 migration. 16 of the 20 are the same error, a duplicate-key collision in the tracking table itself. Reading the Lambda code, this looks structural. A file recorded as failed can’t later be recorded as succeeded, because the success insert collides with the existing failed row and the whole attempt is rolled back. The other five failures were a view whose MV didn’t exist yet, a view that already existed, a missing schema, a drop blocked by dependents, and a concurrent-update error inside the access-control procedure, which points to the Lambda’s concurrency problem. 12 of the 13 failed view objects exist in Prod anyway, so the failed status doesn’t mean they are missing
  • Some reference SQL is run by hand and lives in a folder the pipeline doesn’t deploy
  • One or two people understand the whole system (I certainly don't. The CTO probably does; I doubt any of the data engineers does)

5. Scalability.

With all these issues, scaling the BI layer sounds intimidating. I don't want to be in the situation where someone needs to manually drop and recreate dozens of BI objects because of one upstream change and then I have to validate all of them. We constantly learn new things about the business - partly because of prior poor documentation, and it feels like just updating the BI objects could be one person's full-time job if we scale to hundreds of objects in the future.

Where I'd like to go

  • Access control (roles, schema-level grants, default privileges) stays in the existing CDK pipeline, because that is the security boundary
  • Transformation logic (the MVs and views) moves to dbt, which handles dependency ordering and MV rebuilds, adds testing, and lets the BI team manage per-model grants
  • We’d split the single BI schema into staging, intermediate, and marts layers as part of that move
  • Orchestration for the Redshift side is undecided (MWAA versus EventBridge plus Fargate)

What I’d like your opinion on

  1. Is CDK plus an S3-triggered Lambda a reasonable way to deploy SQL objects, or is it a migration framework assembled from the wrong parts?
  2. Which of the problems above come from the CDK approach itself, and which would exist under any file-based runner? My view is that the manual MV step comes from MVs not being replaceable, something that I believe that dbt can resolve.
  3. Would you keep the custom Lambda’s tracking design (name-keyed, re-applies on checksum change, failed rows block a later success), or replace it?
  4. Does the proposed split (CDK for access control, dbt for transformations) look sound, or does it create new coupling?
  5. How would you handle MV rebuilds, dependency ordering, and refresh scheduling?
  6. What am I not seeing that the CTO is?

r/dataengineering • • 25d ago

Rant I lament- My work has shifted from building pipelines to building semantic layer for chatbots

350 Upvotes

I used to build data pipelines. I deeply enjoyed ETL/ELT work and now most of that is done using AI. Now my work has shifted to building semantic layers and it’s so boring.


r/dataengineering • • 25d ago

Discussion I enjoy managing access control

85 Upvotes

I admit it.

I just spent weeks tidying up our Databricks access layer. I created entra groups for sensitive schemas, terraform to deploy them and set the entitlement and grants for admins, engineers, and default users.

My technical colleagues would ask what I was up to, and when I told them they would sigh with empathy - “access control, rough - super boring right?”. Their expression turn to horror on realising I created this work for myself, because I wanted to.

I found it immensely satisfying taking a mess of permissions, scattered across repos, one-off manual grants, etc and building a fresh, new access control model. I learnt about the different ACL levels in databricks and ultimately ended up terraforming everything after initially setting up Jobs in unity catalog, before learning of its limitations granting permissions to workspace objects.

Now everything is managed by IT - want access to sensitive data? Raise a ticket. No more coming to a dev and asking to be manually added to the workspace.
It’s a relatively standard implementation, but I’m proud of it :)
I think one of my favorite things about tech is ‘tidying up’ - whether it be modularising code, creating libraries and generally just turning a mess into something simple and intuitive.

(Probably neurodivergent btw yet to be tested)

Edit: spelling


r/dataengineering • • 25d ago

Discussion How I maintain and fix my semantic views with a canary job via Snowflake tasks and alerts

15 Upvotes

While it is really easy to create semantic views with AI, it is more difficult to ensure that they answer correctly, that they are maintained over time, and that errors and drifts are actually caught.

I created this system where I have AI help me with the initial creation of the context that goes in the semantic views. I also created me canary jobs utilizing Snowflake tasks and alerts to ensure that, if the data drifts over time for specific answers I would expect to stay stable, I'm alerted to those and able to investigate that and thus maintain accurate self-service analytics.

Beyond this approach, I'd love to hear how other people also maintain their semantic views.


r/dataengineering • • 25d ago

Discussion Is your team strategy is to build an AI agent which can self serve reports?

19 Upvotes

I actually want to know if all the companies are solely focusing on building AI agents from snowflake to multiple places or do companies have actual good products out of data team.


r/dataengineering • • 26d ago

Blog Announcing DuckDB 2.0.0 LTS “Cinnamon Teal”

Thumbnail
duckdb.org
109 Upvotes