Skip to content

docs: services: update diagram - #348

Open
flomonster wants to merge 1 commit into
masterfrom
fam/update-services-diagram
Open

docs: services: update diagram#348
flomonster wants to merge 1 commit into
masterfrom
fam/update-services-diagram

Conversation

@flomonster

@flomonster flomonster commented Aug 11, 2026

Copy link
Copy Markdown
Member

Diagram modifications:

  • add S3
  • add openFGA
  • add core's valkey dependency
  • remove editoast's osrdyne dependency
  • adapt rabbit-mq from scalable to paas solution
  • revamp style
image

@Castavo

This comment was marked as resolved.

- add S3
- add openFGA
- add core's valkey dependency
- remove editoast's osrdyne dependency
- adapt rabbit-mq from scalable to paas solution
- overall revamp style

Signed-off-by: Florian Amsallem <florian.amsallem@gmail.com>
@flomonster
flomonster force-pushed the fam/update-services-diagram branch from 5352a75 to 543932d Compare August 14, 2026 15:05
@Castavo

Castavo commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

nit: I feel like labeling core as workers undermines it's importance

@flomonster

Copy link
Copy Markdown
Member Author

nit: I feel like labeling core as workers undermines it's importance

@bougue-pe @Erashin An opinion on that? Do you have suggestions?

@Erashin

Erashin commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

nit: I feel like labeling core as workers undermines it's importance

@bougue-pe @Erashin An opinion on that? Do you have suggestions?

Yeah nah it is correct, core pods are a bunch of workers, and I don't really think it undermines it that much/don't care. Petition to rename Workers to Worcores though... 😁

I also can't wait for when we'll finally be able to remove the Java logo from the core box. Hopefully in the next couple of months if we have the time.

@flomonster
flomonster requested review from Castavo and Khoyo August 18, 2026 07:46

@Castavo Castavo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking the time to update the docs ❤️

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: maybe external would be more accurate than PaaS ?

For example in our deployment, RabbitMQ isn't PaaS per se

Comment on lines -21 to -22
Coming soon:
- [ ] Adapt `editoast-stateful` so editoast is fully scalable.

@Castavo Castavo Aug 18, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: We can have n instances, but editoast-staleful isn't per se scallable yet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants