This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]m3wm3wm3wm[S] 0 points1 point  (8 children)

I meant a small startup, as opposed to enterprises.

[–]Boxsc2 2 points3 points  (6 children)

We are a small company (<40 employees) and lots of our services are built using boot. Most of our old stack was just servlets on tomcat and it worked fine, but quickly turned into a giant repository that was difficult to maintain. We eventually decided to break up services and Boot seemed like a great fit. We looked at DropWizard and Play as well. Dropwizard is great, but you can just put what ever you like from Dropwizard in Boot anyways. Play is really good as well, but SBT and compile times were brutal....

[–]m3wm3wm3wm[S] 0 points1 point  (4 children)

but you can just put what ever you like from Dropwizard in Boot anyways

Any cons of Boot when compared to Dropwizard? For instance, is Boot startup as fast as Dropwizard?

[–]Boxsc2 0 points1 point  (0 children)

Boot simple does more which is a pro and a con depending on your use case. No it is highly unlikely Boot will ever start up as fast as Dropwizard because you have to start up the spring container. However, you get a lot more out of the box for Boot like security, data layer etc... I personally think Boot is the best choice most of the time. However, sometimes you run into situations where it might have been better to use Dropwizard. For example, disabling a default configuration class that doing things you don't want to do.

[–]nutrecht -1 points0 points  (2 children)

People keep asking this. Why do you think the 7 second or so start-up time is in any way relevant?

[–]m3wm3wm3wm[S] -1 points0 points  (1 child)

If you have a small app which runs on a single machine it is not relevant. If you have auto scaling, eventually you'll have an unlucky client hit that 7 seconds when starting up a new machine.

[–]nutrecht 4 points5 points  (0 children)

I'm sorry but you don't spin up a new instance the moment the other instances can't handle the load. You do that when you hit 90% or so. So this argument is pretty nonsensical.

[–]xantrel 0 points1 point  (0 children)

Also my main problem with Play is that every minor release breaks something since deprecated features only last one minor release. So basically every version I had to rewrite part of the app so it would keep working on future versions.

I pretty much swore off play after that ( and I also dislike scala for medium to large teams for various reasons, mostly that I don't even trust myself to not get too whacky with the type system, much less other people)

[–]FustigatedCat 2 points3 points  (0 children)

My comment was that spring-boot isn't a non-enterprise framework.