Over a million developers have joined DZone.

Reporting From the Groovy/Grails Experience

· Java Zone

Microservices! They are everywhere, or at least, the term is. When should you use a microservice architecture? What factors should be considered when making that decision? Do the benefits outweigh the costs? Why is everyone so excited about them, anyway?  Brought to you in partnership with IBM.

I'm sitting in Scott Davis' session "Real World Grails" on the first day of the Groovy & Grails Experience organized by No Fluff Just Stuff. Scott's been busy today; he did a keynote after lunch.

It's been a great start so far. There's a lot of excitement about Groovy & Grails here. Some attendees have been using Groovy or Grails. But many attendees are here to learn about Groovy & Grails for the first time. Tonight and tomorrow night there will be hands-on coding sessions where the developers present here are invited to get together with their laptops and create their first Grails application. I'm excited to see how that turns out.

As always Jay Zimmerman and his team have an excellent organization for the conference here at the Sheraton Reston hotel. The venue is great, the found is great. The only thing we have to worry about is enjoy the conference and network.

Update: Scott's getting some excellent questions about Grails in this session. It's very exciting so be part of this. Expect more updates from the 2G Experience here on GZ.

Happy coding!

Discover how the Watson team is further developing SDKs in Java, Node.js, Python, iOS, and Android to access these services and make programming easy. Brought to you in partnership with IBM.

Topics:

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}