This article is the fourth in my series on Git for Connection Magazine. It talks about security for your Git installation and how you can lock down your code very effectively, while making it available to only those who need it.
Your NonStop should not be an isolated part of your organization. It participates in a backbone used to move software between systems and eco-systems. Git is a facilitator of this structure. In my third article for Connection Magazine, I explore the details of this structure.
The title may not make any sense, on the surface, but when you consider software to be sausages, with all kinds of stuff inside, do you really want to know what goes into it? This is a core philosophical question that troubles the DVCS communities (git in particular). My latest article in Connection talks about that.
We are currently putting the finishing touches on Auto-Tune R1.6. When it is released, we will give you one month of free time and updates so that you can enjoy trying the new C++ capabilities.
Biggest news in this release? Dynamic SQL support for C and C++. You will be able to scan some of your strings for SQL statements and get plans without having to cut and paste into mxci.
As we look at 2015, we cannot help but see x86 chips in the crystal bowl. And those will be a really interesting challenge for us all. How are we going to refit all of our development, QA, and production systems with copies of our new infrastructure? Or are we? It turns out that virtually all of your current native Itanium code will build and run on the x86 platform. That is good, right? Absolutely. It means you can keep developing at a breakneck pace – no waiting, no stalling, this is NonStop people – and then when your x86 machines show up, switch the build settings in ECLIPSE over to the new target and get right into integration testing. But wait, what if you are not in ECLIPSE yet?
Fortunately, you have some pretty awesome partners out there to help with this effort, including us. This includes people who know how to migrate off of code 100 compilers to workstation development including, yes, BASE24. We know, because we are one of them. We have been building ECLIPSE-based solutions for NonStop since 2004.
But the question came up a few months back: Whyever did you pick NonStop, of all platforms? Interesting but long story. A shorter one would be: Why did you stay with NonStop? That is a good one. Thanks for asking. NonStop represents the Massively Parallel Processing (MPP) a class of systems that is the future of Big Data. Without architectures like ours, we could not possibly hope to deal with the imminent BrontoBytes of data that are headed our way. The multi-core per logical processor structure further affords a strong measure of reliability for extended-mission-critical applications. Most imporant to us is the strong operational discipline that exists on NonStop for always-available management of which other platforms only dream. That means Bigger, Stronger, Faster! But there are really only three critical success factors to keeping systems running: Process, process, and process. That is why we are here.
Savings comes from moving to workstation development.
Process is why we do what we do. Nexbridge started with a strong process focus, and our original services reflected that. We stayed with NonStop and build products around a significant gap in sound processes, that still exists – how do you build large-scale reliable production hardened applications using (now 2015) technology while reducing price-points? Everyone wants to save money, and that savings comes from moving to workstation development. Yet, the risks from inappropriate source-code visibility to deployment errors to simply a lack of technology presents challenges to NonStop. Solving that is also why we are here.
Whether you need products or OSS and workstation development services, we are here.
By adding SQL/MX Auto-Tune to our ECLIPSE suite, we have made SQL performance evaluation simple for C, C++, and Java developers, architects, and managers. Use it to evaluate how plans change over time or between different database; compare statement efficiencies; and try different performance options without having to modify your code.
Don’t forget our ECLIPSE Pathway Plug-In, which provides definition, management, and monitor of Pathway subsystems.
And for those heavily into the original NonStop DDL, our ECLIPSE DDL compiler allows you to preserve your investment and move into workstation development quickly and efficiently.
We are sorry to say that the test.reconciler plug-in has been removed from the Juno update site for compatibility reasons in the underlying ECLIPSE Compare infrastructure. It is still available in Indigo but will be discontinued when that site is deprecated June 2015. If you have issues with that, please contact us.
Auto-Tune R1.5 is now available. We have created a new and improved Java parser for SQL/MX statements that works with the native ECLIPSE facilities. The parser is available as a separate plug-in under JDT Connectors on the update site. Users can also run SQL statements from existing code. Parameters are managed for you and preserved as part of the plan history data. We have a limited, but representative set of supported data types – Please let us know ASAP if you need one that is not supported, via our Contact form or in a comment here.
ECLIPSE Mars is coming fast, and you know what that means. Juno will become the lowest level of support. Our plan is to certify our products on Mars and then drop the Helios and Indigo sites around 25 June 2015 to coincide with the aging off of those two ECLIPSE releases. NSDEE 4.0 will also become the oldest support level at the same time. Please let us know ASAP if this presents a problem – we have no plans to age off the repository branches for those releases at this time.
Welcome to 2015! Release 1.4 of the SQL/MX Auto-Tune plug-in has come out of our build machine and is now on the update site. We had to make a significant change to the plug-in extension point for this release, but since there are no production extenders, at this point anyway, the impact should be minimal. Please let us know if this is an issue and we can provide a backward compatible version. Note: We normally do not make incompatible interface changes, but this was a functional omission that needed to be corrected.
Connection sharing and profile management are significantly improved with this release and people are encouraged to upgrade.
What does Git mean for NonStop? It is a fundamental game changer, that allows NonStop servers to participate in the global ecosystem of software development. No longer in isolation, NonStop now is an active participant in the world of Open software development.This is the first is a series of four articles I wrote for Connection Magazine on the topic.