News for hackers. Stuff that matters.

A comment on Apollo: Spotify's Java libraries for writing micro-services. Parent comment

Re:Apollo: Spotify's Java libraries for writing micro-services by j_jochem on Wednesday December 16, 2015 @09:55AM (#10744581)
If you compare the "Getting Started" sections for both frameworks (Dropwizard's is here: http://www.dropwizard.io/0.9.1/docs/getting-started.html), it looks like the initial setup for Apollo is a lot less complex. This may be a significant advantage, because it cuts down project setup time, which is one of the annoying parts of microservices.

However, I can imagine having to pay for this once you need some more advanced features. Dropwizard comes with a lot of stuff for configuration management and integration, which I guess is mostly missing in Apollo.

[ Parent | on HN ]
Re:Apollo: Spotify's Java libraries for writing micro-services by ones_and_zeros on Wednesday December 16, 2015 @11:22AM (#10745243)
Really? The dropwizard example looks almost identical except for an extra Config related class (which seems like a more sane design to me) and 2 extra methods to implement. Not sure I'd call it a lot less complex.

I think what is happening is the getting started guide for dropwizard looks significantly more indepth than the Apollo guide, covering some features that are entirely optional (and may not even be supported by Apollo.)

[ Parent | on HN ]
Re:Apollo: Spotify's Java libraries for writing micro-services by bjoernw on Wednesday December 16, 2015 @04:29PM (#10747503)
Project setup time with microservices really shouldn't be the issue. Build one template then use for all your services. Don't pick your framework because of setup time (plus I want to argue the differences are minor).
[ Parent | on HN ]