The new Technology Radar is here!

25 01 2015

The new Technology Radar is realeased: http://www.thoughtworks.com/radar/techniques. My impressions are:

Languages an Frameworks

– ‘Adopt’ Java 8,

AngularJS in its ‘trial’, encouraging you to use it

– Spring Boot after a year of official release in the ‘assess’ phase – its maturity still waiting to be confirmed

– on the contrary – JSF in a hold phase

Techniques

Microservices assessment (HOLD) is very interesting:

“We remain convinced that microservices can offer significant advantages to organizations, in terms of improving team autonomy and faster frequency of change. The additional complexity that comes from distributed systems requires an additional level of maturity and investment. We are concerned that some teams are rushing in to adopting microservices without understanding the changes to development, test, and operations that are required to do them well. Our general advice remains simple. Avoidmicroservice envy and start with one or two services before rushing headlong into developing more, to allow your teams time to adjust and understand the right level of granularity.”

I tend to agree with all statements, regarding my experience with microservices, but ‘hold’ phase is a little bit to stringent.





Microservice architecture discussion

23 08 2014

Microservice architecture is a quite new concept which currently I am fond of. I am gaining more and more experience and practical knowledge about its strengts and weaknesses as well. Until the system is deployed, still new conclusions appear.

And new articles appear on the web. I would like to share an article that is a proof that not everyone sees microservices the same way. There are of course new challenges in such design, totally different than in plain old monolyth apps, and of course big advantages. Thiere is a trade off – What is better.

Here is an article, woth reading to know other’s opinion on topic: http://contino.co.uk/microservices-not-a-free-lunch/

 

Surely not everything should be done as microservice, not everything fits, but I am afraid that authors’ doubts make him think that monolythic is not that bad. I mean, Iagree with arguments that API design is a challenge, however good API is crucial for an app, for a class and for system! this makes system responsibilities well defined, clear and testable.

So mostly I agree with author that these are challenges, however in my opinion microservices requires a good, well defined design from developers. Implementing a good design is challenging and not easy. Good software development is not a free lunch, neither are microservices. So I do not agree that things described in article are something new for developers. We all follow good designds. Aren’t we…?








%d bloggers like this: