Who makes the decisions about software architecture in your company? Is it the management? Specialized software architects? Special team members maybe or external consultants? Vote now!
In this article Michael Simons discusses how modern programming paradigms make software patterns not superfluous but easier to understand and less prone to error. He also shows how to make use of Java 8 Lambdas to create a very simple implementation of the factory pattern and a somewhat more complicated version of a builder pattern implementation.
In business, to complete a big project, we segment it into digestible parts. We break our big tasks into smaller autonomous pieces and split up teams by talent. We do this in our daily lives to stay on track and to make sure that we don’t miss anything, so it’s a no brainer that microservices are a rising trend in software development.
Software architect Rainer Stropek discusses the impact of REST, and explains the importance of selecting the right technology to become an expert in.
How much time have you wasted just trying to understand someone else’s source code that needs changing? Veteran software architect Dr. Carola Lilienthal discusses why software architectures need to reflect the human mechanisms for learning and understanding.
Do you enforce an architectural blueprint over the lifetime of your applications? Apparently, its rarely done according to Alexander von Zitzewitz. Here he explains why more love for your architecture can result in better quality projects that are easier to maintain.
What is the right technical and cultural response to the failure of a highly available system? At the JAX London, software architecture expert Jeremy Deane lead two sessions on the importance of resiliency and the challenges of technical change – we spoke to him about diffusion techniques and blameless work culture.
Why are post-its yellow? And what does that mean for product managers? How much of the code that we write actually makes a difference? And what is the whole point of IT? We look back on six key learnings from the first day of the main JAX London conference.
If your software system is slow and struggles to ‘evolve’, there’s a good chance your team is only working one-dimensionally, says Gernot Starke, a leading expert in software architecture behaviour.
As application architecture continues to undergo change, modern applications are now living in increasingly distributed and dynamic infrastructure. Meanwhile, DNS and traffic management markets are finally shifting to accommodate the changing reality.
Somehow, the buzz surrounding microservices has us believing that every single employee and enterprise must break up their monolith empires and follow the microservices trend. But it’s not everyone’s cup of tea, says JAX London speaker Holly Cummins.
A recent IDC study has shown that a converged infrastructure can bring cost reductions and organisational benefits for IT teams. Mark Thurmond from VCE takes a look at the latest findings in IT infrastructure.
For all the great strides that IT is taking to bring us to better futures faster, it turns out that everything we need to know about high-performance system architecture can be learned from the history of urban Paris.
Considering a change in your architecture? If you’re looking at Apache Spark, it might be worth seeing what Alex Zhitnitsky has to say about the top 5 things you should consider before the jump. Software architecture is hard.