The 2015 Architecture Stack: What We Kept, What We Dropped
Article summary
The 2015 Architecture Stack: What We Kept, What We Dropped As the year winds down, it’s a good time to reflect on the architecture choices we made-what stuck, what didn’t, and what’s likely to shape the way we design systems going forward. Here’s a snapshot of what we leaned into, what we walked away from, and where we see the road heading. What We Kept RESTful APIs (with some Swagger) REST continues to be our go-to for service-to-service and client-server communication. The addition of Swagger for interactive documentation and API contracts made onboarding and collaboration smoother across teams. Dependency Injection Everywhere DI has become second nature in most of our server-side apps. It’s helped us cleanly separate concerns and test services in isolation. Containers like Autofac and SimpleInjector have proven lightweight and effective.
Read Full Article on MediumPractical takeaway
The main idea behind The 2015 Architecture Stack: What We Kept, What We Dropped is to help teams move from broad theory to clear, repeatable decision making. When teams apply this thinking, they reduce ambiguity and focus on improvements that deliver measurable momentum.
Example scenario
Imagine a team facing competing priorities. By applying the ideas in The 2015 Architecture Stack: What We Kept, What We Dropped, they can map dependencies, identify risks and choose the next move that produces progress without destabilizing their system.
Common mistakes to avoid
- Trying to redesign everything instead of taking small steps.
- Ignoring real constraints like incentives, ownership or legacy systems.
- Creating documents that do not lead to any change in code or decisions.
How to apply this in real work
Start by identifying where The 2015 Architecture Stack: What We Kept, What We Dropped already shows up in your architecture or delivery flow. Then pick one area where clarity would reduce friction. Apply the idea, measure its effect and share the learning.
Signs you are doing it correctly
- Teams make decisions faster and with fewer disagreements.
- Architectural conversations become clearer and less abstract.
- Changes land safely with fewer surprises or rework cycles.