Inheritance is a powerful feature of the OOP that is used to achieve code reusability. But it is not always the best tool for the job. It is safe to use inheriance within a same package, and the reason is because super and sub classes are under the control of the same team (Or even a same developer). The issues are started when the developer of the super class and sub classes are different teams. It may occur that super class has not been designed to being inherited. So what kind of problems may occur when we extend the class which is not devoted to be inherited.

When we use Spring Security in a standard way, it performs quite a standard actions. For example, Spring Security blocks the un-authenticated requests to the resource (URL resource) and redirects (with 302) to the /login page. But sometimes we want different behavior. Customized behavior such as if the requester is web-browser we want to redirect them to the /login page. But if the requester is not a browser and purely generates RestAPI type of request, then redirection would have no sense. Of course, we could have written some logic on the requester client side to consider 302 as non-authorized behavior.

I have found combination of these three is a quite interesting topic. Actually four, because usually Spring Session is used with Spring Security. There are many resources for Spring Session storing in Redis, but when it comes to storing session in Json format not many infos are there. I have found some but I felt they were not good enough to finish up practically.

As a developer I think Netflix done great job about bandersnatch. They have designed a complex story map, where the story flows and the user who watches the movie can choose the direction of the flow. Definitely there will be many critics about this decision of the Netflix. Because many people will think that movie is the art which must created by artist and watched only with a single flow. What Netflix has done with bandersnatch is new type off art called interactive movie, but it sounds more like a description to the technology. Could be given more fancy specific name.

We will need a UserDetailService implementation, which depends on each development requirements.

Today I’m starting the series of Spring-Security articles, and most of them will be references from web-sites and book named “Spring-Security” from authors Mick Knutson,Robert Winch and Peter Mularien. Before going into an example of Spring Security lets clarify why do we need spring security.

The book has been written by Sam Newman, who talks about microservice architecture usage around the world, including in organizations like Netflix, Amazon, Gilt and the REA group, who have all found that the increased autonomy gives huge advantages to their teams. While I was reading this book, I got the similar feelings to the books such as “Clean Code” and “Clean Architecture”. The author has collected many useful experiences about microservice architecture, some of them very familiar to us, but some of them are gives us “aha” points.

The book was what I have expected from infrastructure book. There were no source codes, except some configuration scripts. The book contains the collection of experiences about cloud-native solutions. It mostly talks about development and deployment processes on the cloud-native.

Korean Open Source Software Conference has gathered many open source communities and contributors. It has become common for conferences these days have tracks: AI, BigDATA, Blockchain, Cloud. This conference was no exception. I have visited cloud development related topics.

Conference organized by NHN Enterprise (Intercontinental Seoul Parnas 19.11.2018) has encompassed many different topics. I have especially was interested in java related topics. How the big tech companies like NHN itself would approach the issue regarding to Oracle recent declarations about Java becoming non-free anymore.