InfoQ Homepage Presentations IO State in API Architecture
IO State in API Architecture
01:39:24
Summary
Owen Rubel talks about IO state that can be shared, cached, synced and reloaded on the fly for all architectural instances without having to restart any instance. This greatly improves automation, performance and flow of API applications and architecture.
Bio
Owen Rubel is an API Architect/Evangelist and Grails Developer.
About the conference
This is a one-of-a-kind conference for application developers, solution and data architects: people who develop business applications, create multi-device aware web applications, process vast quantities of enterprise data, design cloud architectures, and manage high performance infrastructure. The sessions are specifically tailored for Developers and Architects using the popular open source Spring IO Projects, Groovy & Grails, Cloud Foundry, RabbitMQ, Redis, Geode, Hadoop and Tomcat technologies. Whether you're building mission-critical web or business applications, crunching huge amounts of distributed data, or designing the next killer cloud native application, SpringOne2GX will keep you up to date with the latest enterprise technology.
Jan 09, 2016
Community comments
Don't pollute your controllers!
by Dem Pilafian,
Must listen
by Venkateswara Rao Desu,
Don't pollute your controllers!
by Dem Pilafian,
Your message is awaiting moderation. Thank you for participating in the discussion.
This is truly great stuff... "IO state" radically simplifies your controllers by pulling the API definition out into a reloadable configuration, which is inherently more flexible and intuitive.
Must listen
by Venkateswara Rao Desu,
Your message is awaiting moderation. Thank you for participating in the discussion.
Good to know the ideas..