SDK: Guardium SDK for neighborhood security?

https://securityintelligence.com/neighborhood-watch-uniting-the-data-security-community-through-software-development-kits/

Quoting:
"A Neighborhood Watch for the Data Security Community

Today, there are four use case categories of interest for which we are prompting business partners to build apps: risk discovery and classification, new data sources and platforms supported for data protection, big data aggregation and analytics, and industry-focused compliance solutions. These four use cases can be addressed in a variety of ways.

For example, apps can be built to present a combination of internal and external data in tables or visualizations. They can also integrate data from external products or services for better analytics and/or compliance. In addition, apps can be built to host security rules or highlight anomalous activities and send reports to an external source.

The final piece of the puzzle is the skills and expertise of the business partners and developers themselves. Without collaboration from those who are looking for new challenges and innovative ways to contribute to the data security community at large, we can’t move forward. Much like the Neighborhood Watch, the security world needs to band together as a community to ensure that data privacy and security principles are upheld.

So what are you waiting for? To get started, download the Guardium SDK."

More info:

https://exchange.xforce.ibmcloud.com/hub/extension/cd46ff5905e6709be66ab814da9eabb4?cm_mc_uid=78223798062015236497989&cm_mc_sid_50200000=44250091523649799017

Quoting:
"IBM X-Force Exchange is a threat intelligence sharing platform that you can use to research security threats, to aggregate intelligence, and to collaborate with peers.

Logged in users have integrated access to all the functionality of the site: searching, commenting, Collections and sharing. Guests can search and view reports only."

OSS: Integrating Open Source in Commercial Software (Risks)

Very interesting article explaining the risks of using OSS in commercial software (typically closed-source):
http://sdtimes.com/open-source-commercial-software-development-handle-care/

Quoting:
"licenses fit into two major categories: Permissive and Copyleft. With Permissive licenses, there are few terms and conditions. With Copyleft licenses, the terms and conditions tend to be more stringent and bind any derivative work to the same terms and conditions."
(...)
"Mitigate Your Legal Risk
You can mitigate your risks by following some key steps. Some best practices:

1. Track all third party software included in your distribution and the license type, and keep it up to date. Consider each addition carefully, examining the risks and the benefits. Be sure to republish the license text of each work (and subwork), particularly if you are distributing object code only.
2. For Apache works, be sure to republish a copy of the Apache license, together with a prominent notice on any modified files that you have changed the files.
3. Consider the use of any GPL work in a closed source application very carefully. If your application can be considered and extension of the GPL work, you may be required to disclose your source. Seek counsel if your rights are in doubt.
4. Is the project supported by a specific group of developers and is there a thriving community dedicated to delivering a quality application? Or, is the software built by a single developer as a part-time project? 
5. Are contributions well vetted and under CLA? Consider the effort and expense of replacing the software should you encounter any issues. Can it be swapped out easily, or is it intimately entangled with your application? Consider the value of the contribution when compared to self-developed or commercial alternatives. Could you benefit from vendor engagement and professional support?"

SW Design: What is Mule ESB?

If you don't know what a service bus is good for, then you don't need to know Mule ESB. A Service Bus can be a wise integration strategy for loosely coupled information systems:

What is Mule ESB? | MuleSoft

SW Construction: AlchemyAPI ("API as a Service" example)

API as a Service are interesting things (services) to be integrated in external information systems, and that typically that are paid per use. One example is AlchemyAPI: AlchemyAPI - Wikipedia

PS. A white paper on Alchemy API with which I have been spammed (not spam but almost). Note: Requires registering:

The Rise of PhD APIs: How AlchemyAPI Is Contributing To The Next Phase Of The API Economy
APIs are no longer just a development tool. In this white paper from ProgrammableWeb, you can learn more about the rise of PhD APIs and how they harbor game-changing potential for organizations and business models.

BOOK: Patterns of Enterprise Application Architecture (Fowler)

For Enterprise Design Patterns this book is a must:

• http://www.amazon.com/Patterns-Enterprise-Application-Architecture-Martin/dp/0321127420/ref=pd_bxgy_14_img_3?ie=UTF8&refRID=03P48V22NYWE65KC0NV4

Citando:
"The practice of enterprise application development has benefited from the emergence of many new enabling technologies. Multi-tiered object-oriented platforms, such as Java and .NET, have become commonplace. These new tools and technologies are capable of building powerful applications, but they are not easily implemented. Common failures in enterprise applications often occur because their developers do not understand the architectural lessons that experienced object developers have learned. (...)

The topics covered include

·  Dividing an enterprise application into layers
·  The major approaches to organizing business logic
·  An in-depth treatment of mapping between objects and relational databases
·  Using Model-View-Controller to organize a Web presentation
·  Handling concurrency for data that spans multiple transactions
·  Designing distributed object interfaces"

BOOK: Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions (Woolf / Hohpe; 2003)

For successful integration of several information systems and/or data the use of enterprise integration patterns will help for sure:

• https://en.wikipedia.org/wiki/Enterprise_Integration_Patterns
• http://www.amazon.com/Enterprise-Integration-Patterns-Designing-Deploying/dp/8131725081/ref=dp_ob_title_bk