Magento Architectural Discussions, 10 Apr 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Magento Architectural Discussion -- April, 10, 2019

Description

- Updates to Tech Guidelines
- Tech Stack upgrade strategy
- Simplified backward compatibility rules

https://github.com/magento/architecture/issues/139

A

So architectural meeting.

A

So one item I just.

A

Discovered we already discussed it previous meetings about service contracts and.

A

Api interfaces in a separate modules in a separate module, so I proposed some changes to to the update that we have as.

A

Cases such as, if module already has those like new.

A

Folder, they don't have.

A

Api classes, taking into different modules.

A

I think it's about.

A

That one, then also we can go through some proposals, so one is like a great strategy. We had some discussion about it.

A

For tracking updates for dependencies that we have- and in this case is for as I remember, he covers at least composer by city provinces, but you can understand it in the future, so his ideas to use the kind of water it's like what is a service that can track dependencies in composure and automatically create a pull request dependencies. So the idea is that it can create those.

A

Concerns that we had were addressed, which was not creating our note in our own I, think about everything else. We can look at it in the future and just.

A

Approve here, okay, so you'll sink the branches.

A

So there are questions about about our meetings and tomorrow you can find that where you can find them so I just wanted, and you probably can ask.

A

My understanding is that everybody should have access to this calendar and.

A

You can ask architecture in team.

A

And anybody wanted to discuss anything else.

B

Very small data, technical, very Lance, okay,.

C

D

You want to share this.

D

D

D

Can I can rephrase it like this will exist, so it will say as possible to create we've been creating an integration feature. It's possible.

A

A

A

I'm, just thinking about community as well all the issues every.

D

A

D

Working I, say might make sense is because we can be able to things we can have we we can offer something, as is always, something can be offered as a service or service can be just part of a team context. It's part of our interpretation, Magento and import/export.

D

So it's what we compose, we have certainly ever say, but.

D

It cannot say suspect, but to say it wouldn't make sense in this case.

D

Service is not services, services.

A

C

E

Vibrating sis I don't understand, maybe we need some more specific requirements, famous ones.

D

Just the environment, yeah.

E

To the user of his boss of what.

D

They said implementation details.

D

You talking about title of the section or the specific item like this item. Was it the title.

D

Facing this way, we'll say: face Samson like if it's possible to implement integration or feature as a service. It should be clear what.

E

About if we are talking about magenta core features.

A

E

You are on the right doing you negative right calculator, for instance,.

D

We can say.

D

We need to release.

D

We can say that this is it.

A

And here we can cover that should be like platform to provide the interfaces to substitute something with the service right or different things. Everything related service isolation can be covered here that they should consider part of magenta to be deployed as a separate service. But this is.

D

Do two things: one thing is that we want one possible not to add more functionality in which a person can release functionality without releasing magenta and making upgrades. And other thing is.

D

D

That that's one, that's one yeah. Another thing is a similar thing, but it.

D

Will be just not exposed to too much also customers in this case magenta will just work with this service, but we still get benefits of updating the benefits of upgrade upgrade instance, Ferguson, partying, omission and another case when we have a service, and this service exposes interface on how many magenta, just like early education. In this case, it would be possible to also upgrade the service independent and everyone will get updates.

D

Instead, then do two things that yes.

A

But we should consider I think.

F

Yes, I think it makes sense. It also makes sense for for yeah. That's actually.

F

The good thing about it is so we should tell both internal developers extension developers system integrators that new behavior should be not added as extensions of magenta, but as yes but I, think you should. We should reward.

F

New functionality should be added to magenta through separate services and expand for core developers for extension developers and for size. What does it mean for them? So you, you could add a thin extension to Magento and and then you do and then you deploy a separate service.

F

Like in general, everyone both extension developer society and core developers to develop new behavior by adding a light extension thin extension that putting as much behavioral mm sure that should be recommendation for everybody. Let's think I'm just trying to say that we should expand this. It shouldn't be one sentence there should be and at the fit like you know the on the tail section here. You definitely because people will not understand it.

D

Okay, I expand it and.

E

This is for situations it's this, but this what exactly recently this statement require require greater explanation of this communication should looks like because, right now, before we don't have a service is elation down.

E

It's kind of not achievable goals. Why is that I don't know? Maybe this is Croatian how I can write my mic station is a service by using Magento a I understand how I can't ablated Mozilla service visa so out.

F

E

F

E

F

E

Means that we we promote in to them to start develop an extension not not as a Magento extension, but mostly as a independent application and integrators and depending a platoon or through the synclines. Yes, that's exactly what.

F

E

Okay, so maybe we can write this down.

F

Well, so that the proposal is to write it down right, I mean, or do you mean the description, write down the description, description well.

G

F

The specific moment I think we should so we got we best proposal. There was a discussion. Please take a look and imagine if, if there is no other comments,.

E

F

Seen I haven't checked at the latest comments here, but ice. It looks like we can match it. Maybe get some updates, but well I. Don't think there was anybody against it. Okay,.

D

That's a new document. It was submitted to each other in the scope of service ovation.

E

D

Then we made it more. Generic I was working on this proposal. Here is radiant prototype and instead of this proposal, but.

E

Externally, yep I did idea of performance measurements, which pulls small improvements in this area, so I I want to do more more tests, but but but but I believe this is not what I'm going to do it in in the official day. So.

E

E

Area for improvements here, but but I, don't mind, assume I have a stick.

E

Don't have a results which shows significant performance and promise; no, no, no sense to keep it, but but still I I would like to clarify the situation with security because looks like that's III. Don't understand why we cannot use and sterilize and nobody from security. You can provide me and clearance work. It's like blah blah blah in case some time. We do we put it here, but how something can be put it here in case we're using xml or we expected.

E

E

D

This proposal looks good, I reviewed it mix-ins, but we decided to discuss if we want to want to fix them. Spaces, composition,.

D

Matches proposal at this question as a to-do item, for instance, and investigate this question.

A

So what do we do? We need to decide. We hit the group of people to decide.

A

D

I wasn't sure if we introduced if we introduced module, that will simplify processes, unit basis, resolve spaces.

A

D

D

But it will get nice spaces, but the problem we have, we have also different types, not a name. We probably know friends are other things if we cannot remain and how we need to make sure that we do not have plugins his problems, his configuration, because what? If we? What? If was, he is somewhere as a part of configuration, what what would mean build everything in head properly and we will be able to have only one figuration.

A

As far as I remember, this proposal is fine, but it relies on.

G

G

A

Opinions here it now, let's maybe discuss mr. Geiss, put such such items on architectural discussion meetings as well. It's important to discuss so the year.

A

As you know, we have a rule about not introducing breaking changes, especially for services in Parsons of of components.

A

This time we observed that some in some cases we want to do still some changes. So, for example, we have constructors and adding a parameter or optional constructor, which is dependent clause, is considered right, a breaking change if we just follow the same rules, rules for constructors for all other methods, but it really.

A

A

For everything else to.

E

My point: that's you know. Actually we have a problem. This is a upgrades and, if I'm Thomas still on this meeting, he confuses.

E

Upgrades between patch versions, so my point: he have to keep.

E

Keep semantic version shaker clear, clear between patch releases. Maybe we have to communicate this properly to product organization, so it's better to do a minor visa releases more often, and then they are doing right now, but actually actually even they had a conversation with Evans users.

E

We we have a several tasks in progress which will definitely bring bring Tom and by patent compatibility in our system in two to three to two, and this is because of strict requirement from product side, so decisions touch disease differences definitely do you'll complicate a great process, so this is kind of trade off in case we want to get a better upgrade process. We we have to stop doing changes.

E

You know in our budget releases like this in case we don't care about this. Definitely yeah. We can. We can approve such changes, but you know that's it. Changes like this may may may affect may affect extensions which won't be able to migrate from one patch version to another patch version.

A

E

Practical part, because actually we have a banal costs of upgrades. So this is not a direct theoretical numbers and we probably know.

A

Yeah but again it's not yes in some, in some cases, changes that we make really break and I, don't think all of them break extensions on this. We do not allow to notify even constructor. It really limits us because you cannot like there is very little what you can do. You can just change an algorithm in inside the method, but you can do more than that. If you limits even bug fixing I, don't.

E

A

Always a product request. Yes, you can consider bug. Fixing is also a product request, of course, but it's something that is expected from part releases. I think it's again like constructors should not be a part of API public API. Usually they are only considered because people extend glasses and from our side we try to avoid that by providing different things, and we still admit that there are cases where it's impossible. For this case, we.

A

Just I just think that we need to find the balance.

E

I believe we have a pretty good solution in case we will be able to run more minor releases.

E

We have to communicate its that's okay, guys in case we have a one minor release for two years, so we upgrade.

E

Because we are.

A

Reliability for.

A

And your other opinions, and still here.

F

I'm trying to read the proposal, so all changes are approved by text by the way it's a considerable model of private.

F

A

G

Require two dependencies and do we direct instantiate the object manager.

E

Constructor but is outputting arguments it's your compatible, but MV will be able to opens.

D

D

Think also the idea of it as much, but but they sometimes it's hard to it's hard to see like why why it would be a problem if everyone for.

G

Somebody but extension customers more to based on this. This not depend which is not is which is not present in previous patch girls. Let us know in the case know if you, if someone would.

D

D

A

A

Okay, anything else, if not done I, think we're done thanks all you next time join us for.