Skip to content

Commit 6553a79

Browse files
committed
wip: #55
1 parent dbb55db commit 6553a79

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed

content/posts/meetup-55-wrapup.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,8 @@ tags:
77
- meetup
88
---
99

10+
### OpenCloud
11+
1012
Hybrid Meetup #55 took place
1113
[2025-10-28](https://www.meetup.com/de-de/leipzig-golang/events/305626267) 19:00 at
1214
[Basislager Leipzig](https://basislager.co) and we had a great presentation by
@@ -22,17 +24,19 @@ installations to large clusters with millions of users.
2224

2325
The presentation reflected on some architectural and deployment changes over
2426
the years - densily packed with engineering wisdom that extends beyond code and
25-
include aspects like deployment, backwards compatibilty and scalability.
27+
includes aspects like deployment, requirements and project constraints,
28+
backwards compatibilty and scalability.
2629

2730
<!--
2831
2932
[![](/meetup-55-opencloud/screenshot-2025-10-31-112307-opencloud-landscape.png)](https://docs.opencloud.eu/)
3033
3134
-->
3235

33-
Some highlights from the presentation:
36+
### Background and origins
3437

35-
* [reva](https://reva.link/) is a CERN storage interop layer and is also where opencloud story started
38+
* [reva](https://reva.link/) is a CERN storage interop layer and is also where
39+
the opencloud story started, many years ago:
3640

3741
> Reva is an interoperability platform consisting of several daemons written in
3842
> Go. It acts as bridge between high-level clients (mobile, web, desktop) and
@@ -64,7 +68,9 @@ forked](https://www.linux-magazin.de/artikel/opencloud-forkt-owncloud-neue-wendu
6468
6569
More background on CERNBox: [Turning CephFS into a collaborative space with
6670
CERNBox](https://www.epj-conferences.org/articles/epjconf/pdf/2025/22/epjconf_chep2025_01041.pdf)
67-
(2025)
71+
(2025).
72+
73+
### Highlight from the presentation
6874

6975
* not uncontroversial: you can get rid of a database at the core of your application (which was, in parts, a bottleneck) and move to a file based setup (plus lots of caches)
7076
* moving from individual shares to the concept of spaces opened up a more maintainably way to handle users (and users that left)

0 commit comments

Comments
 (0)