Symfony Finland
Random things on PHP, Symfony and web development
Today the world has evermore information created and consumed each passing day. Not only is content creation using tools like Instagram, YouTube and others booming, but we're also collecting more and more data using sensors in our smartphones, cars and what not. So what is the relation of these two, content and data?
Today the market is awash with options available for developers to consume content using the APIs. Some go as far as describing their offering as a CMS without the bad parts, where as some choose to provide content using a data centric API platform.
All of this while the classic Content Management System players are opening up their core via APIs and modernising their technical platforms. Is there a silver bullet for Content APIs? Let's find out!
RESTful APIs are on the lips of everyone currently. Everyone is got one or will have one very soon. They are always underlined as being full REST APIs. But if you're not fully utilising your API internally, is it really complete and a priority for you?
As more and more processing is moving over to the client side you're more likely than ever to need to expose your back end resources via an API. The top of mind is application data, but you'll likely need to get endpoint URLs and translations as well. Or maybe you don't, but you should - manual maintenance is laboursome and error prone.