December 07, 2014

Service Architecture – The Importance of Standardized Modeling – Part I
Having the Technical Contract and the Descriptive Contract as two separate standardized definitions allows a more effective design of the Service Registry [REF-2], allowing the alignment of the Service & Capability Profiles [REF-2] and underlying meta-data structures to each one of them, as per "Metadata Centralization" design pattern [REF-1]. It will also enhance the use of an Enterprise Repository of Service-related meta-data and documentation, on which the explicit categorization would ease its overall structure definition and governance. Each of these parts will be explained below.

Todd Montgomery on the Reality of IoT, Protocols, Nuklei
we have things like Raspberry Pis, where the amount of compute power that we have, the amount of storage and the amount of RAM is non-trivial, I mean it’s much more then even back in early 90’s that you had or even early 2000’s. So these really aren't as constrained as they used to be, so the game is different, but we still have these devices that are running on limited power supplies, so things like how the radio is used, how the CPU is used, how much RAM is used, these actually have much more of an effect on battery life than other things. And that’s something that you can't just throw away, a device is only good as long as it’s operating, if it can only operate for half an hour a day, that’s kind of annoying.

Developing Microservices for PaaS with Spring and Cloud Foundry
Microservices - small, loosely coupled applications that follow the Unix philosophy of ""doing one thing well"" - represent the application development side of enabling rapid, iterative development, horizontal scale, polyglot clients, and continuous delivery. They also enable us to scale application development and eliminate long term commitments to a single technology stack. While microservices are simple, they are certainly not easy. It's recently been said that "microservices are not a free lunch." Interestingly enough, if you look at the concerns typically expressed about microservices, you'll find that they are exactly the challenges that a PaaS is intended to address.

Managing Firewalls Shouldn't Push Risks to the Extreme
IT security and operations teams are not adrenaline junkies tempting fate. Without solid network performance, operations staff can’t deliver required application service levels to users and customers. And without a comprehensive security solution—which includes multiple security technologies working collaboratively—security teams have little chance of combating the Advanced Persistent Threats (APTs) that increasingly use Advanced Evasion Techniques (AETs). Given today’s budget limitations and resource constraints, some IT managers think they have no choice but to maintain performance at the expense of security by turning off key firewall security features such as Deep Packet Inspection and Application Control.

Faster than a speeding bullet: Geolocation data and account misuse
By tracking the geographic location for account logins, it is possible to discover anomalies by calculating the distance between two logins from the same account. If the speed required to travel that distance within the allotted time is unlikely or impossible, this can indicate account misuse. This use of geolocation data can augment other monitoring techniques to detect malicious behavior on a network. This paper explores how such calculations can be made, identifies parts of the process requiring special consideration, and highlights what can be revealed when using geolocation data to monitor account use.

Lies, Damn Lies And The Myth Of Following The Data
We are told to follow the data and the truth will be revealed, but data tells many tales and it depends on the data and how you interpret it. It makes me wonder if anything is definitive if you can present two similar sets of data and draw wildly different conclusions, depending on your emphasis. That’s because data is a tool in the hands of humans and we can interpret it as we choose. And to be clear, this isn’t because we choose to be deliberately deceptive either, although that’s probably true sometimes. It’s because being human, we can bring unintended biases to the data. It’s a huge conundrum in the age of big data. How do you find definitive answers when you can look at different data points on the same topic and come to different interpretations?

Introducing the Agnostic Composition Controller Pattern
Speaking of practical aspects of the presented separation, it is important to mention that it is actually based on the common threefold notion of basic SOA: client-requestor, service-worker, and service registry. Everything is simple in basic SOA. The client could be anything, capable to comprehend and comply with the service-worker contract, the worker doesn't have to be REST or SOAP WS, and the service registry (and its taxonomy) is not compulsory at all. Frustratingly, the large majority of SOA practitioners openly neglect service registry as "redundant and hardly useful." That might be true for simple service activities in basic SOA.

The Fatal Flaw of Finalizers and Phantoms
Objects with finalize() methods require more work for the garbage collector to track, and the execution requirements of the finalize method require that the garbage collector keep all memory associated with it around until execution has successfully completed. This means a collector is typically required to revisit the object, likely in a whole separate pass. Consequently finalizers on objects with large instance counts and short lifespans are likely to introduce major performance problems.

Security in 2015: The Internet Becomes the Corporate Network Perimeter
The entire concept of the corporate perimeter is changing. We used to think of the perimeter as simply being the actual physical or logical perimeter of the corporate network. A few years ago it became more common to think of the endpoint device as part of this perimeter. Today, smart CISO's recognize that the internet itself is truly the perimeter of their network. So the internet is where we must look for the solution to this rapidly evolving security problem. Businesses today are looking for a comprehensive layer of protection through the cloud itself - enabling users to be protected wherever, and however, they are connecting to web services and applications.

Showdown coming on Ethernet standard for faster Wi-Fi
Most likely you'll have a choice of 2.5Gbps (bits per second) and 5Gbps, and there's no debate there. Some vendors have already announced components and designs for such products, but there's no guarantee that systems built with parts from the two camps will work together. Enterprises want to be able to mix and match gear from any vendor they like, so the official IEEE group for Ethernet standards voted last month to form a task group to set a standard. Now, the two rival camps will have to work out which technologies go into the standard and which don't. This isn't the first time that competing teams of companies have pushed different approaches before a common specification is set, but that kind of rivalry sometimes leaves potential buyers waiting.

Quote for the day:

"Most execs think customers come first & employees second. This is a real concern." -- Nicholas S. Barnett

No comments:

Post a Comment