Login | Register   
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


advertisement

More articles by Jason Bloomberg

Author Bio

Jason Bloomberg is the leading expert on architecting agility for the enterprise. As president of Intellyx, Mr. Bloomberg brings his years of thought leadership in the areas of Cloud Computing, Enterprise Architecture, and Service-Oriented Architecture to a global clientele of business executives, architects, software vendors, and Cloud service providers looking to achieve technology-enabled business agility across their organizations and for their customers. His latest book, The Agile Architecture Revolution (John Wiley & Sons, 2013), sets the stage for Mr. Bloomberg’s groundbreaking Agile Architecture vision.

Mr. Bloomberg is perhaps best known for his twelve years at ZapThink, where he created and delivered the Licensed ZapThink Architect (LZA) SOA course and associated credential, certifying over 1,700 professionals worldwide. He is one of the original Managing Partners of ZapThink LLC, the leading SOA advisory and analysis firm, which was acquired by Dovel Technologies in 2011. He now runs the successor to the LZA program, the Bloomberg Agile Architecture Certification Course, around the world.

Mr. Bloomberg is a frequent conference speaker and prolific writer. He has published over 500 articles, spoken at over 300 conferences, Webinars, and other events, and has been quoted in the press over 1,400 times as the leading expert on agile approaches to architecture in the enterprise.

Mr. Bloomberg’s previous book, Service Orient or Be Doomed! How Service Orientation Will Change Your Business (John Wiley & Sons, 2006, coauthored with Ron Schmelzer), is recognized as the leading business book on Service Orientation. He also co-authored the books XML and Web Services Unleashed (SAMS Publishing, 2002), and Web Page Scripting Techniques (Hayden Books, 1996).

Prior to ZapThink, Mr. Bloomberg built a diverse background in eBusiness technology management and industry analysis, including serving as a senior analyst in IDC’s eBusiness Advisory group, as well as holding eBusiness management positions at USWeb/CKS (later marchFIRST) and WaveBend Solutions (now Hitachi Consulting).

For Agile | July 18, 2014
Making up new words for old concepts – or using old words for new concepts – goes on all the time
For Agile | July 9, 2014
Well-planned technical debt is actually a good thing
For Agile | July 7, 2014
We finally have a recipe for technology-supported innovation in even the stodgiest of enterprises
For Agile | July 3, 2014
REST is rather vague about many of the specifics of its implementation
For Agile | July 1, 2014
You must analyze the risks inherent in making the change under consideration as well as the risks of not making the change
For Agile | June 26, 2014
Once the SaaS vendors figure out how to offer full-fledged mass customization while maintaining a commoditized code base, enterprises won’t have to settle for any color as long as it’s black any more.
For Agile | June 25, 2014
It’s possible to solve the agility-killing software customization problem
For Agile | June 20, 2014
Individual people and pieces of technology don’t exhibit business agility, organizations do
For Agile | June 18, 2014
Agility is harder than it sounds, especially when legacy runs the business.
For Agile | June 12, 2014
The notion that information technology is the business is a point that underlies the entire Bloomberg Agile Architecture vision
For Agile | June 9, 2014
The Bloomberg Agile Architecture Technique offers a way of thinking about and doing architecture that is laser-focused on business agility as the fundamental business driver.
For Agile | June 3, 2014
For many organizations there’s a fundamental disconnect between the next-gen digital vision and the reality of today’s intractable legacy-centric business.
For Agile | May 27, 2014
The real risk is moving too quickly on a modernization effort, where stuff will break.
For Agile | May 14, 2014
The reason Agile software architecture will never be agile is because it is by necessity focused on building software. In other words, it’s caught in a Catch-22 that it will never escape.
For Agile | May 8, 2014
Agile Architecture pulls together all the elements into a coherent, realizable story for implementing technology-enabled business agility across the enterprise.
Sitemap