BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Programming Content on InfoQ

  • A Business Perspective on APIs

    This article, the first of a new series, examines APIs from a business perspective, whether or not they are open and overtly monetized. It covers the importance of tying your APIs back to your business value, looks at the type of data that should be used, and studies the success stories of Amazon and Twilio.

  • Article Series: Web APIs: From Start to Finish

    This series takes the reader on a journey from determining the business case for APIs to a design methodology, meeting implementation challenges, and taking the long view on maintaining public APIs on the Web over time. Along the way there are interviews with influential individuals and even a suggested reading list on APIs and related topics.

  • Git and GitHub LiveLesson Review and Q&A with the Author

    Git and GitHub LiveLessons, published by Addison-Wesley Professional, is a video course based on a live workshop given by Peter Bell. No previous experience with Git or other source code management tools is assumed. Here, we present the course content and finally ask a few questions to the course's author.

  • Introducing Essence#: A Smalltalk-based Language for .NET

    There are two basic schools of thought when it comes to Object Oriented Programming: the method based Simula and the message based Smalltalk. The Simula school is well represented in .NET by C# and VB. With Alan Lovejoy’s Essence#, we can see what a Smalltalk inspired language would look like on the CLR.

  • GS Collections by Example – Part 2

    Donald Raab, creator of GS Collections, open sourced by Goldman Sachs in 2012, continues to explore more examples from that powerful framework

  • Testing the Internet of Things: The Human Experience

    Mobile and embedded devices, more than any other technology, are an integral part of our lives and have the potential to become a part of us. This article discusses what “human experience” testing is and is not, and uses concepts from human computer interaction design theory to establish a framework for developing “human experience” test scenarios.

  • Stats Anomalies Detector

    The article describes the general outline of the Stats Anomalies Detector we developed at MyHeritage and provides a detailed explanation of how to enhance the code (will be available soon at MyHeritage GitHub) to meet your company’s needs.

  • Java 8 for Financial Services

    Java 8 lambdas and the new Streams API simplify common idiomatic constructs. In this article we investigate some common use cases in financial services and how they are easily solved with lambdas and Java 8's new Stream API.

  • Virtual Panel on App Development

    Mobile apps are everywhere and a company can hardly ignore them as an additional or even as the primary channel to offer services. Whereas it’s clear that one has to support Android and iOS to reach a maximum of users, it’s not quite clear, what technology and tools to chose to build applications for those systems or whether to go “native”, “hybrid” or “HTML/JavaScript” ...

  • SQL Server Source Control and Deployment with Visual Studio

    The holy grail of database development is the ability to treat database objects (tables, views, stored procedures, etc.) as if they were just like any other form of source code. While SQL Server Data Tools doesn’t quite that level, it gets very close.

  • Sam Newman: Practical Implications of Microservices in 14 Tips

    What are the practical concerns associated with running microservice systems? And what you need to know to embrace the power of smaller services without making things too hard? At last GeeCon 2014 in Krakow, Sam Newman tried to answer those questions by giving 14 tips about how microservices can interface, how the can be monitored, deployed, and made safer.

  • Why Some Web APIs Are Not RESTful and What Can Be Done About It

    Many Web API designers claim their are RESTful, but their APIs have little in common with REST. What can be done to make a web service API truly RESTful?

BT