It really depends on the market you're in. Some markets (first I can think of are betting/gambling/banking) are very much against change. If you work in that sector you have two choices: 1) you resign and you go work with your friends in a startup working 24/7 but with the freedom to choose the tools you like (my choice) or 2) you fight to start adopting the technology and process you like in some non-core-business minor project. You have to prove on the field why your choice is better, and you can use the opportunity to learn at the same time. The more experienced you are, the more you know that you only know pros and cons of technologies after having used them in real -albeit small- production environments.
I think the same applies to big companies (in general) that have "old school" operations departments. They cannot fire the "websphere certified experts" out of the blue. If you work in a more open minded company, you could do a POC yourself. I setup a cluster with ansible, docker, consul, a 3-node elasticsearch cluster, akka/scala standalone apps and redis (all of them containerised) in a couple of days. If you show that you can type "vagrant up" and seamlessly create and provision N VMs with your clustered app and maybe show how easy it is to upgrade the cluster by simply typing "sbt docker:publish" and "ansible-playbook .... playbook.yml" they could be impressed. It doesn't take more than a couple of hours a day for 1 or 2 weeks (depending on your experience) to build something like that to show off. The management is always more impressed by devops than code stuff, imho. *Build something, show 'em!* Cheers G On Friday, 8 May 2015 16:55:46 UTC+2, Patrik Nordwall wrote: > > Hi Jacobus, > > I like your analogy of putting a Ferrari on the back of a truck. However, > you can unload the Ferrari when you have reached the racing track. If you > can't convince them that it is easier and better to run Akka outside the > JEE container you can use the JEE Container for deployment, only. > > One way is to use a ServletContextListener that creates the Akka > ActorSystem (and Akka Http server endpoint) when loaded and stops it on > unload. > > Regards, > Patrik > > On Fri, May 8, 2015 at 2:48 PM, lutzh <lutz.h...@gmail.com <javascript:>> > wrote: > >> Hi Jacobus, >> >> If you can look behind the somewhat provocative title, I think Eberhard >> Wolff gives a pretty comprehensive overview of why you should look beyond >> app servers in "Java Application Servers Are Dead": >> >> http://jaxenter.com/java-application-servers-dead-1-111928.html >> http://jaxenter.com/java-application-servers-dead-112186.html >> http://www.infoq.com/interviews/eberhard-wolff-java-app-servers >> >> A bit too focused on Docker for my taste, but also valid: >> https://medium.com/@jstrachan/the-decline-of-java-application-servers-when-using-docker-containers-edbe032e1f30 >> >> Hope this helps, >> Lutz >> >> >> Am Mittwoch, 6. Mai 2015 20:51:01 UTC+2 schrieb Jacobus: >>> >>> Hi there, >>> >>> I'm hoping that someone can help me with advice on motivating why >>> containerless services makes sense. I'm trying to motivate writing a new >>> business service on Akka-HTTP, but other architects stands rock solid on >>> the argument that only services that can be deployed inside Websphere >>> Application Server must be allowed. Now, I realise I can probably make >>> Akka-HTTP run inside a JEE container, but that will be like putting a >>> Ferrari on the back of a truck. >>> >>> Their primary concerns are mostly around deployment, configuration, >>> monitoring, etc. They also have a sense that things are just safer in >>> Websphere for some kind or reason. They still think in terms of queues and >>> transactions, etc. >>> >>> If anyone can give me some good business, operational or technical >>> motivators, then I will be very grateful. Also, if you are aware of any >>> stat's, benchmarks, etc. on this, then that will help too. Maybe groups >>> like Gartner have done a bit of a writeup industry moving away from >>> containers? >>> >>> Anything that can help will be greatly appreciated. I need some solid >>> facts and ideas to back my statements. >>> >>> Thanks in advance. >>> >>> Cheers, >>> Jacobus >>> >> -- >> >>>>>>>>>> Read the docs: http://akka.io/docs/ >> >>>>>>>>>> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user >> --- >> You received this message because you are subscribed to the Google Groups >> "Akka User List" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to akka-user+...@googlegroups.com <javascript:>. >> To post to this group, send email to akka...@googlegroups.com >> <javascript:>. >> Visit this group at http://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > > Patrik Nordwall > Typesafe <http://typesafe.com/> - Reactive apps on the JVM > Twitter: @patriknw > > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
