On behalf of the selection teams for Modern Application Development, I am pleased to share this exciting, dynamic, and diverse set of developer-related breakouts, workshops, BoFs, and labs for Red Hat Summit 2018.
With these 61+ sessions listed below, we believe that every attending application developer will come away with a strong understanding of where Red Hat is headed in this app dev space, and obtain a good foundation for tackling that next generation of apps. Encompassing various aspects of Modern App Dev, some sub-topics we’ve focused on are around microservices, service mesh, security and AI/ML, plus there is a large collection of complementary and related topics.
So…if you’re an application developer, we invite you to attend Red Hat Summit 2018 and experience the code first hand. There’s something for everyone and definitely something for you. Register today.
Great talks don’t happen without great speakers, and we feel really privileged to have these popular, high-in-demand speakers:
Continue reading “Red Hat Summit 2018 to focus on Modern App Development”
This article lists the most common methods in use to version your API. Its intention is not to convince you to use one or another but rather to provide a comprehensive list of the methodologies used, together with some of their advantages and disadvantages and some additional references for each method as well.
Continue reading “API versioning methods: A brief reference”
The API field progressed in leaps and bounds in the past with impressive new APIs, standards advances, conferences and unfortunately also more negative events like security breaches. Given all that activity, it’s a tough call to guess what might be next. What’s certainly true is that there will be more growth in store! There were already prediction pieces out there for 2016 like Yves de Montcheuil’s, Neha Sampat’s great 10 API predictions presentation at APIDays Paris and Mark Boyd’s great piece on the potential economic impact of APIs in 2016.
APIs are showing up in a wide range of future projections in all sorts of industries from financial services to data centers and healthcare. We’re also expecting a bumper year for API growth. However, this still leaves questions: what the growth areas will be, and what will be important to get the most out of 2016 for APIs? Here’s our shot at 2016 API predictions:
Continue reading “2016 API predictions”
From the buzz on Twitter and blog posts, you could feel that ECMAScript 6 was finally coming. It has many things we’ve wanted for years, so it makes sense to start new projects with it in mind.
Continue reading Rails + jspm >= ECMAScript 6 awesomeness
In previous parts of the series, we covered the need for APIs to be valuable, have business models, and be easy to adopt. In this post, we’ll cover the next items on the list: API management and API management tools:
This is part four in our “Golden Rules for Great APIs” series (see links at the end of the article), and it tackles a subject which is very easy to pay lip service to but very difficult to deliver on:
Continue reading Building great APIs, part IV: Great developer support
Last week’s “Building Great APIs” article covered two of John Musser and Adam Duvander’s 5 Key Elements of great APIs: providing value and having a business model. In this post, we’ll tackle the next topic:
- Make it simple, flexible, and easily adopted.
The three statements seem obvious until you begin to unpick what they mean–and they might even seem contradictory. Making an API simple seems like a noble goal but it can easily be thwarted by complex edge use cases, existing legacy code and a tendency on the part of some API designers to expose underlying data models in raw form. Flexibility often breeds complexity as the API becomes overloaded to meet many use cases. We’ll take each topic in turn and finish up with an all-important metric: TTFHW (Time To First Hello World).
Continue reading “Building great APIs, part II: Simplicity, flexibility, and TTFHW”
Back in July, John Musser wrote an excellent post over at ProgrammableWeb on what it takes to build great APIs (also check out his OSCON slides on Slideshare). John boils what’s needed down to five key elements—value, plan and business model, flexibility, good management, and great support.
Together with perhaps just one more–stability (an unreliable API is as good as unusable)–these points arguably should represent an “API Gold Standard” for almost any API program. Getting these right goes a long way to running a great API program and we advise anybody running an API to think about them.
Continue reading “Building great APIs, part I: The gold standard”