The last Python Architecture you will ever need?
davidvujic.blogspot.com
The last Python Architecture you will ever need?
1–10 of 26 posts
Re: The last Python Architecture you will ever need?
#2Can't see what it actually does that's special. 'Watch the videos' isn't as helpful as writing it down.
Re: The last Python Architecture you will ever need?
#3Am I misunderstanding something or does this look like the worst possible incarnation of a monolith? Everything seems to be sharing everything, so whenever you modify anything, everything is impacted. Which in turn, means that a developer who wants to make any changes, has to understand the whole system in order to not break things or make a mess - which of course leads the cautious developer to write new, duplicate code for the piece of shared functionality that they want, defeating the whole purpose.
Happy to be corrected, I hope I'm wrong.
Re: The last Python Architecture you will ever need?
#4As far as I understand this is Python specific.
Most monorepos I work with do not use a single language but many. It's pointless to use multiple tools for the same thing instead of one that works with all languages, like nx for example.
Re: The last Python Architecture you will ever need?
#5I am not smart enough to full understand what this does? I just don’t full understand the use. Does someone have a good rundown of how this would help me?
Re: The last Python Architecture you will ever need?
#6Okay, I gave it 10 minutes and tried to find out what "Polylith" is about, skimming reading material found by following down links starting at the PyPi page.
What I found was 10 minutes of LEGO-bricks analogies.
What I didn't find, is an answer how this is supposed to be that much different from Microservices or libraries.
https://polylith.gitbook.io/polylith/
Polylith addresses these challenges by introducing simple,
composable, LEGO-like bricks, which can easily be shared across
teams and services. The choice of bricks determines what each
artifact does and how it's exposed.
And if it doesn't, isn't this just describing a module/package/library?
Sure, I mean, the idea of having all these libraries in one repository is neat, but...where is the difference from having all of them externally, in their own repos, and leaving the rest to the build pipeline?
Again, this is just based on what I found in 10 minutes of lazy skimming, so if anyone wants to point out something important I overlooked or didn't understand, I'm happy to be corrected.
Re: The last Python Architecture you will ever need?
#7Okay, I gave it 10 minutes and tried to find out what "Polylith" is about, skimming reading material found by following down links starting at the PyPi page. What I found was 10 minutes of LEGO-bricks analogies. What I didn't find, is an answer how this is supposed to be that much different from Microservices or libraries. https://polylith.gitbook.io/polylith/ Polylith addresses these challenges by introducing simple…
Pricely my thoughts too, I think this is just what people do anyway. Talked about from another's perspective. Like marketing an idea. Reinventing the wheel.
Typically not the most ideal option either.
Re: The last Python Architecture you will ever need?
#8Microservices are about the data, not the code. Sharing code is really not an issue. Defining data domain boundaries and data change protocols is the challenging issue in application level architecture. See no mention of data here, so...moving on.
Re: The last Python Architecture you will ever need?
#9Okay, I gave it 10 minutes and tried to find out what "Polylith" is about, skimming reading material found by following down links starting at the PyPi page. What I found was 10 minutes of LEGO-bricks analogies. What I didn't find, is an answer how this is supposed to be that much different from Microservices or libraries. https://polylith.gitbook.io/polylith/ Polylith addresses these challenges by introducing simple…
Thank You. I just spent 10 minutes skimming and was thinking I was really missing something.
Re: The last Python Architecture you will ever need?
#10There is something to be said for questions like "what is the best way to organize code, many small codebases or one big one?". Code can have many properties. It can be easy or hard to read, to extend, performance, scalable and a number of other things.
But poly- or monolithic is a way to describe how the code is organized. It must never be an end goal in itself. That way lies madness.