A developer panel was held at Microsoft Connect() following the multiple annoucements of new features and releases. Microservices and containers are in the center of the discussion, along with Azure, serverless architecture and developer tooling.
Lawyer.com recently announced that they are adopting the HTTP/2 protocol. Gerald Gorman, tech entrepreneur, CEO, and co-founder of Lawyer.com, spoke to InfoQ about their technology implementation, their position on microservices and lightweight containers, their unique search engine, and their use of social media.
Microsoft recently announced the General Availability of Microsoft Flow, a cloud-based automation platform that provides workflow and connectivity capabilities across many popular online and on-premises services. Since the preview, in April 2016, 117,000 people from 61,000 organizations have used the service to automate their business processes.
Amazon has updated their AWS Well-Architected Framework (PDF) based on feedback from clients, adding a new pillar, Operational Excellence.
Microservices has a very long history, not as short as many believe. Neither was SOA invented in the 90s. We have been working with the core ideas behind services for five decades, Greg Young explained at the recent Microservices Conference in London, during his presentation on working with microservices.
When it comes to application security, we often include it as an afterthought. We have learnt how to add test into the development workflows, but with security we often assume someone else will come and fix it later on, Sam Newman claimed in his keynote at this year’s Microservices Conference in London.
Developers attracted to the Azure Service Bus Relay for its ability to expose web services on internal networks to Internet-facing consumers have had, until recently, only one way to build such services: WCF. Using a just-released public preview called Azure Relay Hybrid Connections, developers may now use any Web socket friendly platform to connect local services to this cloud-based broker.
Javier Lopez and Mihail Vieru spoke at Reactive Summit 2016 Conference about cloud-based data integration and distribution platform used for stream processing in business intelligence use cases. Their solution is based on technologies such as Flink, Kafka and Elasticsearch.
Honeycomb is a tool for observing and correlating events in distributed systems. It provides a different approach from existing tools like Zipkin in that it moves away from the single-request-tracing model to a more free-form model of collecting and querying data across layers and dimensions.
Lambda architecture has been a popular solution that combines batch and stream processing. Kartik Paramasivam at LinkedIn wrote about how his team addressed stream processing and Lambda architecture challenges using Apache Samza for data processing. The challenges described are the late arrival of events and the processing of duplicated messages.
Jason Goth, Micah Blalock, and Patricia Anderson of Credera explained at SpringOne how they used Conway's law to tailor a client's technical architecture and processes to reverse falling productivity and accelerate the production of high-quality code.
To drive operational maturity you need a microservices architecture, continuous delivery process, DevOps culture and platform automation. Together these four help you to transform your whole organization for achieving cloud-native operability to continuously deliver additional value to your customers.
Microsoft’s recently open-sourced P language aims to make it possible to write safe asynchronous event-driven programs on Linux, macOS, and Windows.
GitHub recently introduced at their Github Universe conference the alpha release of their new API, written in Facebook’s GraphQL (a query language that allows for self-service API contracts). GitHub writes in its engineering blog that its main reason for switching API paradigms is lack of scalability with their existing RESTful contracts.
Sean Kelly, a Principal Engineer at Komad, has written about his experiences around microservices and five "truths" which developers believe microservices will bring to their architectures, applications and teams, but which, in his view, are not always the case.