Just to give a background, I have been working for a team composed of 15 developers in the financial field where we have a lot of iterations on a single code base. (Unfortunately it is not a microservice) Each of the changes are reflected in multiple branches that we are having trouble tracking them since most of us send pull requests almost every day.
One thing I can think of is a rewrite of our code base where it will be a lot easier to decouple the business logic layer.
Any suggestions or if you can share ideal public repositories I can take a look at, that would be really helpful. Thank you.
I started a series of videos to help us all understand better Design Patterns and learn how and when to properly implement them. It would be amazing to receive feedback about it.
My latest video is the Factory Method Design Pattern: https://youtu.be/ZOwkT2wWe-w
The whole playlist you can find here: https://youtube.com/playlist?list=PLlNZpkgIOuFVRsL2Gq05hCxgt1OyIFtTZ
Looking at https://phptherightway.com/pages/Design-Patterns.html the example shows a static method for the factories create method. This site is widely cited as a good starting point here. Any reason why the example uses static methods? Is this a standard part of this design pattern? It seems if your factory is a bit more complex and you want to create additional methods and maintain a state before returning the object that static is not the way to go.
Factory Method Pattern is organized under creational pattern as it deals with the creation of the object.
This design pattern is based on one of the OOPs concept ie. Encapsulation. Generally, we write object creation code on client side program but in factory pattern, we encapsulate object creation code inside factory method. So depending on the data provided to the factory, it can return an object of one of several possible classes listed in a program. You can consider using this pattern when:
- Your subclasses need to instantiate objects of some classes based on criteria.
- An application needs to have loose coupling between different classes.
Factory Method Pattern by Example
r/https://medium.com/hussy-io/factory-method-pattern-for-token-vesting-smart-contracts-cae2b0361aed
Hi,
I'll try to make the question as general as possible so the language doesn't matter.
I came across a problem which I could solve with a factory, however the factory would need a dependency and need to access this.
So, my understanding thus far was that the method in a factory to create an instance has to be static. But when a method is static I can't use this of course, because it doesn't exist.
Now a co-worker told me to just not make the method static, but tbh, I only learned about the factories with static methods, so I'm a bit confused.
Is it normal/okay to use a factory pattern without static methods? Are those simply two separate design patterns? non-static vs. static?
Thanks!
Hey everyone, looking forward to hear your suggestions and comments to improve my article on Factory Method!
Our 11 year old son was playing the oculus and created some pattern on the headset that we need to input before we play it. He doesn't remember it and we can't seem to get around it. Even on the app I need it to pair with it. Is there anyway around it without a factory reset?
Hi!
I am wondering if this UML-diagram here: https://go.gliffy.com/go/share/sm4frpobsubifu6j6jv8 is explaining well or have everything needed in the Factory method design pattern? Or am I missing something, like methods needed or variables for this example?
I think I have everything, an interface, an concrete class ConcreteProduct, then the factory ConcreteCreator which generates the objects, and then the Creator as an example implementation.
