Ted is the CTO of iTrellis, an IT full-lifecycle management and custom software development shop located in Seattle, WA. He's spent quality time on several different platforms, starting with DOS 3.3 and Windows 3.0, all the way up through the JVM, .NET, NodeJS, Android, iOS, and a few others along the way. He's a programming language aficionado, having written production code in ten different languages, and experiments/prototypes/spikes in a dozen more. He resides in Seattle with his wife, two sons, two pets, four desktops, eight laptops, ten mobile devices, and a rather scary electricity bill.
Everybody wants to build a REST API. But looking at JAX-RS, you see a very thin API on top of the existing JavaEE infrastructure, and not much more. What if you need more? What if you want less? Is it really time to just reach for Spring-plus-Hibernate-plus-SpringMVC-plus.... again? In this talk, weâ€™ll examine three candidates for building REST APIs in Java: Spark Java (not the Hadoop Spark!), DropWizard, and RestX, each with different advantages and levels of support. Never again will you think â€˜just Jerseyâ€™ again.
This is continuation of morning workshop. It is not a separate workshop. You need to be present of both parts as it is a whole day workshop.
Functional programming, objects. HTTP, ESBs. Actors, agents, APIs. Mobile, mobile web, web, native web, native. Building a modern application (that is, one architected, designed, and built somewhere in the next two to five years) is not easy. You could, certainly, do as we've done for years, and just "pick a tech stack, follow the 'best principles', go!". And you could, certainly, rewrite the same code over again in another five years, this time with different 'best practices' and/or different languages and/or different APIs. But it would still be the same code, and it would still suffer the same problems. Or, you could build something different.