The world of software is becoming more disconnected. Be it mobile applications that run on our phone and tablets, or client-side JavaScript applications; the software world is moving to distributed architectures. When done right, these provide scalability and reusability that make applications more efficient to use, easier to write, and tolerant of changes. A well-made REST API can be the center of a rich and complex family of applications and workflows that can make solving even the most complex business problems as simple as playing with Legos. Still, many developers struggle beyond the basics of REST. What makes an API great and how should I structure mine? How do I deal with things like security and scalability? And what about this “HATEOAS” I keep hearing about, is that something I should be using? Also, what is GraphQL and should I care about it? In this session, we’ll go beyond the basic verbs and request/response paradigm and explore how to use REST to build APIs that provide the flexibility and reusability to serve your needs today and for years to come. We’ll talk about how to design a great API and care for it after deployment, and how to answer those questions about “HATEOAS” that might be gnawing at you.
YOU MAY ALSO LIKE:
Build the REST API Of Your Dreams
James Bender
James has been involved in software development and architecture for 18 years. He has worked as a developer and architect on everything from small, single-user applications to Enterprise-scale, multi-user systems. His specialties are .NET development and architecture, TDD, SOA, WCF, Web Development, cloud computing, and agile development methodologies. He is an experienced mentor and author. James is a Microsoft MVP, Chairman of the Central Ohio Day of .NET and former President of the Central Ohio .NET Developers Group. James's book "Professional Test Driven Development with C#: Developing Real World Applications with TDD" was released in May of 2011.