Luca Botti

I have been using Java for the past 25 years, more or less (yes, I am Old...). Watched the J2EE madness...and the micro service reinassance, In the middle I have been grown used to the rich Java ecosystem (Spring, Maven, Hibernate, and so on). How to migrate to Python? Which components of the ecosystem should we choose?

Hi all,

I am still beginning with Mongo (and NoSQL). Coming from old-school development, I have one question - does NoSQL put a lot of burden on developers to keep everything going? Does the paradigm shift the responsibility from shared (Dev: I need field X on table Y - DBA:mmm let me think about it...done) to a Dev only capability to manage it all (often in a lone cubicle)?

Hi all,

I am just asking because Docker, while simple at the start, requires a complete new mindset related to deployment. And, to me, it looks like to be "production ready" it needs a complete devops infrastructure to be effective.
While experimenting from the command line is quite simple, things can get out of control fast, so the complete "assemble-deploy-manage" shall be in place. Not only Kubernetes or Swarm, but also on the Dev side (whatever you use).

Just my thinking.

Regards

Hi Craig,

thanks for your answer. Would it be possible to define a spring-boot context interpreting a web.xml? do you think the effort would be of some value? This way you could maintain a standard web.xml for, e.g., deployment on a Weblogic instance while having (agile) development on spring-boot.

This i just the case I have, doing some consulting work which introduces spring boot to a weblogic production environment. I am aware of (and used) what is described in documentation about deployment to App servers, but I am not allowed to migrate all the configuration to a java based class.

Regards

Is it possible to maintain both the Java Configuration and the web.xml configuration?

This would apply to the following situation:

An older, in built framework but with a newer, Spring Boot based REST api implementation.

Regards

Hi Dmitry,
thanks for the reply.

I am ordering upgrade to v 7 now....

Hi Dmitry,

I have been using Idea since 4.5 (and upgrading afterwards).

Some random toughts:

1) Quality vs features:
Version 4.5 was full of quality (stability, speed...) while later versions (7 included ) have been a swing in other direction. What about taking a pause in features (after all, we have plugins) and getting back to the fast, stable, IDE we had?

2) The Real competion
To all the plugins kids hanging around, the real competition is not Eclipse, which is crawling under its own structure, but NetBeans (admittedly, version 5.5 onward). The NB 6.x stream (rc status) is really similar to Idea for the IDE and for concepts, so people (like me) hating perspectives and plugin (dis)integration are more likely to look at NetBeans than eclipse. Try some of the shorctus of Idea in NB 6....

3) Crazy idea
What about an emulating layer on top of Plugin API to make NB plugins compatible with Idea ?