design-principles

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Multitasking seems to be a disaster at times when big projects crashes due to shared mutation of I would say shared resources are accessed by multiple threads. It becomes very difficult to debug and trace the origin of bug and what is causing it. It made me

This is a design question regarding the implementation of a Pipeline. The following is my naive implementation. Interface for individual steps/stages in the pipeline: public interface Step<T, U> { public U execute(T input); } Concrete implementations of steps/stages in pipeline: public class StepOne implements Step<Integer, Integer> { @Override public Integer execute(Integer input) { return input + 100; } } public class StepTwo implements Step<Integer, Integer> { @Override public Integer execute(Integer input) { return input + 500; } } public class StepThree implements Step<Integer, String> {

I have the following code: interface IService { void Execute(); } class ServiceA : IService { public void Execute() { ... } } class ServiceB : IService { public void Execute() { ... } } class ServiceComposite : IService { List<IService> _services = new List<IService>(); public ServiceComposite() { _services.Add(new ServiceA()); _services.Add(new ServiceB()); } public void Execute() { foreach (IService service in _services) { service.Execute(); } } } The problem is that ServiceB depends on some results from ServiceA. My idea is to create container class for storing the results, then inject it

I know this is probably subjective but I read this optimization page from Google for PHP and they suggest use the variable property directly without the need of getters and setters. Understandably I see the performance gain in this but is this really a good design practice to follow? Their Example using getter/setter: class dog { public $name = ''; public function setName($name) { $this->name = $name; } public function getName() { return $this->name; } } $rover = new dog(); $rover->setName('rover'); echo $rover->getName(); Suggested Optimization: $rover = new dog(); $rover->name = 'rover';