We are now comfortable with JSON as a more flexible alternative to XML. Beyond the buzzword: Reinventing 'service'Ĭut to 2015. And worst of all, web services suffered from complex spaghetti code with an interface that was every bit as messy as before. Vendors couldn't agree on the specifics, which led to incompatibilities. However, web services were plagued by a host of issues. In other words, web services were the bumps on the building blocks-all following the same set of rules, so that regardless of the underlying software, you'd get the benefits of plug-and-play modularity. Web services were a set of XML-based standards that gave existing software an easily integrable interface-at least in theory. The notion of web services from the early 2000s was an important milestone in the Lego-ization of enterprise software. If only we could treat software as Lego blocks, the reasoning goes, we could mix and match various bits and pieces, building flexible applications by simply snapping their components together. Ever since subroutines appeared in early attempts at computer programming, developers have tried to modularize their code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |