![]() One of the most significant conversation pieces about GraphQL is that it isn’t a RESTful API interface. There were no JSON API specific sessions at the conference, but the JSON API maintainers were in attendance to listen and take in information rather than speak. It has also grown in popularity thanks to venture-capital based companies like Apollo which have built server and client tooling around GraphQL. Facebook created the GraphQL specification, and the GraphQL Foundation now manages the specification. One identifiable topic at the conference was GraphQL. One of the most exciting concepts discussed throughout the sessions was the shift of “where Drupal lives in the architecture stack.” Oh, and of course the exciting “battle” between GraphQL and RESTful APIs more precisely for the event, the JSON API specification. It is about using the correct tooling for the exact problem and how do our previous paradigms fit into this new architecture. Moreover, it’s not about abandoning Drupal. The only conference on the future of CMS, headless CMS, and decoupled CMS. The act of decoupling in a system requires specific system design and presents engineering challenges. It is an engineering and design conference. That is one reason it has quickly become a favorite event. Last year saw the phasing out of the word “Drupal” as the conference became focused on decoupling in general, not just Drupal. ![]() Not familiar with Decoupled Days? Spawned in the “Hallway Track” of DrupalCon between its founders, the conference originated as Decoupled Drupal Days in 2017. The conference has quickly risen to be one of my favorite conference of the year. ![]() I had the privilege to speak and attend last year, as well. Decoupled Days 2019 last month, the third edition of the conference, was fantastic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |