I’m offering online training in Cloud Native Architecture via O’Reilly’s amazing Safari platform. Several dates still have openings:
September 6-7, 2017: 12:00pm - 4:00pm EDT
September 13-14, 2017: 12:00pm - 4:00pm EDT
October 4-5, 2017: 12:00pm - 4:00pm EDT
More dates will be announced soon.
Designed for software architects and senior developers working on medium-to-large scale enterprise systems, this two-day, hands-on course will introduce you to the cloud native architectural pattern language and give you practice applying it.
I’m offering a two-day, intensive, hands-on training course at the upcoming O’Reilly Software Architecture Conference in Boston, MS. The class is entitled Cloud-Native Application Architectures with Spring and Cloud Foundry. In this class you will have the opportunity to implement an easy-to-understand storefront system (complete with product search, details, reviews, and recommendations) as a cloud-native architecture using Spring and Cloud Foundry. In addition, you’ll get hands-on exposure to the Netflix OSS family of technologies.
The gauntlet has again been dropped in the world of cloud interoperability. The dueling factions include those asserting that competitors to Amazon’s web services (principally OpenStack) must adopt AWS’s API’s in order to remain viable, and those that believe such “API cloning” will do nothing more than stunt innovation. If you were to ask me, I’d say that we’ve seen this play out before. Remember the “Clone Wars” that began in the late 1980’s and that persisted for the better part of two decades?
One of the great things about Cloud Foundry is that it is a great enabler. Tall words. But what do they mean? Essentially, Cloud Foundry (and any other well-designed PaaS) enables us to do things as developers and operators that would be extremely difficult in a traditional deployment environments. One particularly valuable area of enablement is our new found ability to practice Continous Delivery, meaning that we continuously prove our ability to deliver working software by continuously treating each code commit to a system as if it could be deployed to a production environment.
Wow…it seems I only post to this blog toward the end of May. Well, that all changes now. You see, as of June 3, 2013, this blog is going to become one of many aspects of my new “day job.” On Monday, I start my life as a Community Engineer with Cloud Foundry by Pivotal. What’s a Community Engineer? Quite honestly, I’m not completely sure of the answer to that question yet.
I recently stumbled across the NOSQL Summer website via my friend Alex Miller’s blog. The idea is to setup a summer reading club focused around databases and distributed systems. Groups will gather “worldwide” to discuss various papers and the hopefully submit the substance of their discussions back to the NOSQL Summer website in the form of annotated papers.
This sounded like a great idea to me, so I decided that we’d co-locate a NOSQL Summer discussion with our monthly Memphis JUG meetings.
I gave two lightning talks at CommunityOne today, the first of which described deploying Grails applications to Morph AppSpace.
For the uninitiated, Grails is a Ruby on Rails inspired full stack web development framework which brings “convention over configuration” and “DRY” into the Java web development arena. Unlike Rails, it is not an effort from scratch, but rather stands on the shoulders of proven giants in the Java world like the Spring framework and Hibernate.