I went to DDDX at Skillsmatter and here's Dan Haywood's talk on RESTful Objects - Posted on 25 June 2012.
One of the guys at the round table discussion proposed the question (can't remember exactly) What technology should I choose to ensure that my system doesn't have to change for the next 10 years? Our initial response was to ask a bit more about his application, it was a line of business application that was currently running on the windows desktop that did not have to process high loads and did not have a high volume of users.
Our discussions went from trying to answer the original question to delving deeper into why he needed the change. We discussed what advice we would give for choosing a technology since "Microsoft is dead" (according to some) but then we were looking more towards designing and architecting your system to cope with change better.
Choosing the right technology (1)
It depends! Well that was easy enough, wasn't it, there aren't many questions around technology that can't be answered by that. Well, to be a little bit more specific then it depends on the nature of the solution that you are planning. For example, if you are still focussed on building desktop applications on windows then you are going to have to consider .NET alongside Java or maybe native, if you are going for the new Windows Store applications then you have the choice of C++, .NET, HTML and CSS. If you are going web-based then you can choose from Java, Ruby, Scala, .NET, PHP, Python and many more than I cannot possibly name here.
Does the application that you are writing need to work on multiple different environmnets? Does it need to be distributed so that multiple people are accessing the same system at the same time from different environments? Then we are probably talking either web stack or a cross platform tool.
Are we talking moving into mobile applications? Then actually the .NET runtime may be possibility as thanks to the Mono for Android and MonoTouch allows us to write most of the logic once and then just create a new UI per platform.
So which tech? If you are wanting stability for the next ten years that I do not think that you would want to go bleeding edge, there is a lot of risk that this technology will not take off and get the adoption required, it is likely to change a lot during the early days and case you some serious problems. However, conversely, you do not want to be using something that is dying, though the technology is well understood it will get increasingly hard to find people who know the technology to maintain your product. We are aiming therefore for something fairly popular with a large enough base of developers to ensure that in the next ten years there will be enough people who understand it, also there is a sufficient community who have already encountered and solved many of your problems.
What about coolness? Developers like the shiny new languages and frameworks, we like to see the new cool things and as technologies die we are less tempted to take a job that uses these technologies. There is the concept of the Gartner Hype Cycle which shows how technologies are adopted and their level of maturity. I think we should be looking for a technology on the slope of productivity. It is still fairly new and cool but people are being more realistic about what the technology can do.
Another suggestion about choosing the right technology was to look at the Thoughtworks Tech Radar. This is an opinion blog from Thoughtworks but it shows their current thinking about which technologies should be adopted and trialed but it is a fair representation of what is happening in the world.
To quote Robert Burns' poem To a Mouse:
But little Mouse, you are not alone,
In proving foresight may be vain:
The best laid schemes of mice and men
Go often awry,
And leave us nothing but grief and pain,
For promised joy!
We think, we plan, we forge ahead with our plans because they are our best guess as to what will be useful to us in the future but we do not have the gift of foresight, we cannot guarantee that our choices will be the right ones. Life changes around use all of the time.
If you believe in Agile Development then we are told that change will happen. The focus tends to be on change as a consequence of the business changing their minds, by the world changing and the business needing to change what they require from the system. However, we rarely think of this as the platform, language and frameworks that we are using changing from underneath us. How can we isolate ourselves from these changes?
Architecting for change
A typical situation that we could find ourselves in is that our entire system is built as one massive project, with highly coupled components and has very brief encounters with other languages. This means that any change to the platform is going to cost us severely. We have to change everything. So what can we do?
1. Build a system of loosely coupled components
We need to think of our system as a set of loosely coupled components that interact through well defined interfaces. This allows any change to the platform that may impact only a single component to be isolated within that component. It does not mean that we are safe from the change but it reduces the cost of fixing that component.
2. Define clear APIs
If we are to achieve loose coupling then we are going to have to create the interfaces that I spoke of above. These interfaces form an API around the component, they are the only ways that anyone else can interact with the component. Each API should have a clear design and each call should have a clear purpose. Our APIs should not really expose the inner workings of the component, they should be an abstraction layer (a anti-corruption layer in Doman Driven Design terms) on top of our component's logic.
These APIs could be in the form of a RESTful or SOAP based web service if we are developing a distributed application, or a framework library that only publicly exposes the API to the rest of the world. It does not matter how we do it but the client should only depend on the API (and maybe even then build it's own abstraction layer around the API).
One way to ensure that people do not "do the wrong thing" and dig into the internal structure of the component is to develop the component in isolation from everythying else. The component is developed and published in an independent work space/solution to the consuming components.
3. Test your APIs
A key principle that is being widely adopted is that we should test our systems. A lot of developers are now seeing the advantage of unit testing and people in the Agile Testing world have been pushing Specification by Example, Executable Specifications and Behaviour Driven Development to focus is more on testing our systems to ensure that they meet the functional demands. If we have an API, we should test it thoroughly to ensure that the behaviour, that way we already have the tests should we need to change a component.
By testing, I do mean that we need to test at the unit level but also more importantly testing the APIs in a live like environment, it is no use just testing the code, we need to be able to test the actual implentation, exactly what the clients would talk to.
As an example, assume we have a RESTful API for managing a shopping basket. We write an automated test suite for the API that runs against a web server, let's say for the moment that we developed it in C# and it was running on IIS. If we wanted to move to a Java service then the tests are already there, we can re-implement it safely because we know the behaviour it is supposed to implement. We implement the API in Java and then we switch from the original implementation to the new one. We do so safe in the knowledge that the consumer does not know anything about the underlying implementation and that the new implementation mirrors exactly the original yet we are now free from the original platform.
4. Version your APIs
Versioning the APIs is a key part of being able to loosely couple your components. If you do not version these components the systems become highly coupled through the API when it comes to deployment time. You cannot deploy either the client or the component without the client breaking. With a versioned API you publish the server first and then the clients can make changes as time goes by. Usually the older versions are adapters that change the older message formats into the current versions and the newer results into the older version.
Once again, this does not isolate us from change directly but again reduces the impact of any one specific change.
I mentioned testing the APIs in a "realistic environment" above. Yet, if we are left to do this manually then we will ignore it when we are busy or we will leave it for weeks and do a lot of testing in one go. This not only leaves us open to "human" errors and mistakes passing incorrect functionality, or simply not having time and not testing everything but it also increases our feedback time. If I am updating an API and I break an earlier version, then I need to know as soon as possible so I am more able to find the breaking change.
Each component should be able to be deployed automatically, each component should be deployed quickly to a test environment that is similar to the real one and it should be able to run the suite of tests that we have against it. If we have been conscientious and written the tests (or at least at the time of writing) so we know we have a comprehensive suite of tests a nightly build will let me know if I have broken anything.
Althought this does not directly isolate us from change it enables us to automatically verify that our systems work, and even integrate with each other. If we are wanting to develop and test a new implementation of a component then we should learn how to deploy it, we front-load the risk of learning how to deploy a new technology, we grow our understanding before we are there, on the "go-live" date panicking that we have not worked out how to correctly deploy our application, we have already automated everything.
Choosing the right technology (2)
Given what I have said above I would now ask you the question...
Is there a single "right technology" for your application?
I think my answer would probably be no. There are several possible technologies that could implement each component and I have to then say that we have to look at a good technology in which to implement each component. We do not have to have a single technology stack any more.
We are moving towards having a polyglot of languages, frameworks and paradigms in our systems but each one suited to the individual component(s) that it supports. Does this mean that it will be harder to find developers? Perhaps, but good developers can understand multiple languages and may even be more interested in working in a variety of languages.
Loosely coupled, well tested components, give us the freedom the choose a good technology for each component. It allows us to migrate a component without significantly disturbing any of its clients with reduced effort. Should a platform that several of our components depend upon change it is rarely a sudden and immediate change, we have time to move to a new platform but with this system we can change one component at a time, learning about our new platform as we go.
These are my thoughts about what we discussed in the meeting but I think they portray what we discussed but probably in a little more detail concerning the techniques. I think the discussion was interesting it cemented my views around designing a system around a set of APIs. This gives us the time to play, to try out new languages, new platforms, new frameworks and minimise the risk to our system, it is a technique we can use for prototyping with new technologies and evolving our system as technology moves on.
I went to DDDX at Skillsmatter and here's Greg Young's talk on Event Sourcing being a functional concept - Posted on 24 June 2012.
How many of us find a solution to a complex problem when we are away from our desks? In the shower? With friends? What powers this sudden insight? - Posted on 17 May 2012.
To become more Open we need to get ourselves into a place and time where we are relaxed, in this post I talk a bit about how we do that - Posted on 15 May 2012.
Creativity is at the heat of what we do and often we are the most creative when we are at play as we unleash the power of our imagination. I argue that we should bring play into the business. - Posted on 28 April 2012.