CodeIsGo.com

Eugen Paraschiv wrote this tutorial about securing a REST API with OAuth and consume it from a simple AngularJS client. Tutorials is step-by-step with extensive code examples. It does not explain theory behind the tokens usage in details, but this can be found on Internet.

The application we’re going to build out will consist of four separate modules:

• Authorization Server
• Resource Server
• UI implicit - a front end app using the Implicit Flow
• UI password - a front end app using the Password Flow

We learned how to authorize our application using OAuth2. And as a bonus the full implementation of this tutorial can be found in the GitHub project - this is an Eclipse based project, so it should be easy to import and run as it is.

Full stack engineer, ex-ThoughtWorker, DevOps/µServices under acronym RDX shares his personal experience with a dozen of microservices consultations he was part.

Author states the execution matters, not the approach and one should not just accept the love/hate propaganda. Picking the right tool for the right job makes things easier.

Bad monoliths try to reinvent the world. They think that code and design patterns are the solution to everything. They strive to build reusable components, libraries, and also become a platform along the way. But they usually don’t end up succeeding at any of these goals.

Some examples of above statement and also bad microservices architecture examples in article.

Tom Whitbread’s intro into Elixir. Elixir is a fast, dynamic and scalable language which is fast becoming adopted by the startup crowd and established businesses alike for production applications.

Elixir leverages the low-latency, fault-tolerant Erlang VM, meaning complete access to the Erlang ecosystem used by companies such as Heroku, WhatsApp, Klarna, and Basho.

Article touches few topics like:

• syntax
• scalability
• fault tolerance
• installation
• interactive mode

Hope it will raise enough interest in you to give it a try…

John Krafcik, the CEO of Alphabet’s self-driving car company, Waymo, explained to the Financial Times (paywall) that its vehicles only occasionally connect to the Internet.

Self-driving cars are essentially large computers on wheels. No surprise, then, that some of them will be kept offline in the name of security.

Waymo is able to take its cars offline because its crucial systems are all stored on local computers aboard the car. And since those systems are performing the same job as a human driver—that is, taking in information about the roadway and making decisions about how to behave—there’s no need for it to pull data down from the cloud at every turn.

O’Reilly Data Show - Mike Tung, founder and CEO of Diffbot - talks about extracting structured information from semi-structured or unstructured data sources (“dark data”). Diffbot is dedicated to building large-scale knowledge databases.

Knowledge databases and graphs are built using (semi-supervised) machine learning, and then subsequently used to power intelligent systems that form the basis of AI applications.

Diffbot is at the heart of many web applications, and it’s starting to power a wide array of intelligent applications. We talked about the challenges of building a web-scale platform for doing highly accurate, semi-supervised, structured data extraction. We also took a tour through the AI landscape, and the early days of self-driving cars.

Doug Bridgens post on how to rotate passwords. Rotating application layer passwords is hard. Not because changing a password in some database is difficult, it’s often only a single command.

The benefits of automation in a large infrastructure are easy to talk about, easy to sketch on a whiteboard. The problems start when you attempt to implement your ideas, and then you can find yourself with a seemingly insurmountable sackful of (human) objections and (process) hurdles.

Article sports example code including password rotation of the backend MySQL root password, but the same principle applies to the application node database credentials.

Author makes argument: In a practical sense we’ve improved the security of the infrastructure.

John a De Goes thoughts on what the architecture of modern functional programs should look like.

Article consists of a newly-minted, tricked-out recommendation for architecting modern functional programs, along with new ways of thinking about the structure of this architecture.

It mentions how Onion Architecture can be implemented in object-oriented programming or in functional programming. And continues with 2 choices for functional programming - Monad Transformers Library(MTL), or something equivalent to it (the final approach, though note that the type classes from MTL can be subverted to build Free structures); or Free monads, or something equivalent to them (the initial approach).

A simple example in the onion architecture using Free monads and the Free Transformers approach to abstracting over functor operations is included. The onion architecture has proven an enormously useful tool for structuring large-scale functional programs in a composable and modular way.

Serverless computing become an alternative computing model to virtual machines and containers. AWS Lambda is leader in this area. However, an application designed for Lambda cannot run outside the context of AWS.

For developers considering an alternative that can run within the datacenter and cloud, OpenWhisk from IBM can be a potential option.

Article introduces OpenWhisk concepts and terminology and also has start example of actions which you can create in web browser editor provided by Bluemix.

OpenWhisk is a powerful, open source serverless computing platform

New Relic’s quick intro into serverless performance. Article presents a new challenge to operators and developers: how do you build fast and resilient functions when many traditional system and application metrics are either unavailable or no longer relevant?

Article reads about observing cold start time in the real world. Functions will vary in their execution time, yet all of these functions are identical and run in the same region. The only difference is how often they are triggered from an external API request.

Outcome: Warming the green function had no significant impact on how quickly the external request completed and the warmed Lambda function sometimes responded more slowly than the cold Lambda functions did.

Interesting read.

Meetup is an online service that allows people to gather into groups and meet in person. Since 2002, the company has been growing and its technology stack has been changing. Today, they are in the process of migrating to the cloud, using both Amazon Web Services and Google Compute Platform.

Yvette Pasqua is the CTO of Meetup and she joins the show to explain how Meetup’s technology stack works and how the teams are organized. The discussion of multiple clouds is particularly interesting - Yvette describes GCP and AWS as both having distinct, well-defined use cases at Meetup.