logarhythm

7 ms·

1.
Understanding Polylith through the lens of Hexagonal architecture(medium.com)
9 points by logarhythm 3y ago|2 comments
2.
by logarhythm 4y ago
Thank you for explaining how you work, and I would never laugh at a developer for copy/pasting code. We've all done it! I'm still intrigued to understand exactly how you share code across services. Let's say that you&#x2
3.
by logarhythm 5y ago
Thank you for your comprehensive and detailed feedback! I'll leave Joakim to respond to your comments about his presentation, and I'll respond directly to your comments about the nutshell video. > you've actually never dem
4.
by logarhythm 5y ago
I'm not sure we're understanding each other. When I asked "How does it solve the problem of sharing code across service boundaries?", I meant how does your language or architecture enable you to share code across separat
5.
by logarhythm 5y ago
That's useful feedback, thank you. I'll suggest that change to Joakim.
6.
by logarhythm 5y ago
Have you read the "Advantages of Polylith" page? https://polylith.gitbook.io/polylith/conclusion/advantages-o... It tries to summarise the benefits from both a development and deployment perspective.
7.
by logarhythm 5y ago
Technically, a Polylith interface is a collection of "pass-through" functions, each of which delegate their function call to an "implementation" function within the component. I agree with you that many languages have sy
8.
by logarhythm 5y ago
Which ecosystem do you work with? How does it solve the problem of sharing code across service boundaries?
9.
by logarhythm 5y ago
That's right, it's a highly opinionated approach to building software, which comes with a host of benefits. Including my favourite; a complete untangling of your development and production environments. With Polylith you always de
10.
by logarhythm 5y ago
I was confused because you were replying to a comment which mentioned the "long video", so I assumed you were both talking about the forty-minute one on the homepage of the documentation. My mistake. Did my response to `cjg` in th
11.
by logarhythm 5y ago
The idea with that part of the video was to couch the new concept (components) within the framework of existing concepts (functions, objects, layers, etc.) to try to help people connect the new concept at the right place in their knowledge
12.
by logarhythm 5y ago
Exactly! Components are an attempt at scaling-up functions to a system-level building block, whilst maintaining as many of the benefits as possible.
13.
by logarhythm 5y ago
Your understanding of Polylith is essentially correct. It is a combination of existing ideas, such as monorepos, convention, components, interfaces, encapsulation, and static code analysis. However, I'd argue that what emerged in Polyl
14.
by logarhythm 5y ago
Thanks for the feedback, we appreciate it. It's tricky to pick the right level of detail when explaining an idea like Polylith. If we could precisely identify the level of understanding of the reader, then we could tailor the content t
15.
by logarhythm 5y ago
Before you completely give up on understanding the concept, I would like to suggest you try the 10-minute "Polylith in a Nutshell" video: https://www.youtube.com/watch?v=Xz8slbpGvnk If you watch it at 1.5x speed,
16.
by logarhythm 5y ago
Thanks! It was a bit nerve-racking to give traffic light ratings to existing architectures that people use and enjoy, but I hope we were fair in our assessment.
17.
by logarhythm 5y ago
Thanks for the feedback, and I'm glad to hear that you understood the concept from the text documentation. We decided to include both videos and text in the documentation because we know that people are different, and have different pr
18.
by logarhythm 5y ago
I'm a member of the team that created Polylith, so feel free to ask questions or give feedback. Polylith has been gaining momentum within the Clojure community. As an example, you can follow along with Sean Corfield's journey migr
19.
by logarhythm 6y ago
Polylith is, first and foremost, an opinionated file structure for codebases (similar to how a framework forces you to structure your code in a particular way). Polylith's structure gives a host of benefits for the modularity, composab
20.
by logarhythm 6y ago
We've simplified the architecture, by reducing the number of concepts down to just three: components, bases, and projects. The tool is simpler, gives faster feedback, and a better visualisation of your projects, due to (amount other de
21.
by logarhythm 8y ago
Thanks for pointing this out. I've added that fair play note to the first page of the documentation.
22.
Show HN: Polylith – A software architecture based on Lego-like blocks(polylith.gitbook.io)
5 points by logarhythm 8y ago|5 comments
23.
by logarhythm 10y ago
Nova | nova.com | Web Developer | Stockholm, Sweden | Full-time, on-site Nova is a talent network, which is transforming into a product organisation. We’re building web and mobile apps that facilitate personal and professional development,
24.
by logarhythm 11y ago
Totally agree with your point, but just a quick note: using the thread-first -> macro won't work in this case, instead you'd use the thread-last macro ->>. Also Clojure doesn't have a sum function, so you'd actu
25.
The case for Clojure [video](youtu.be)
1 points by logarhythm 13y ago|0 comments