Posted in Cloud, history, Internet, Networks

The Expenditure of TCPv4

While working on an TCP/IP problem today, I was finally struck by the fact that we have for all intents and purposes expended the entire TCPv4 addressing space. I knew it was coming, years ago, but now while testing IP addresses, it dawned on me.

You can now pick any arbitrary set of numbers nnn.nnn.nnn.nnn and expect a response. Ping them, probe them, something will be there, or it’s being held. All gone, this is the equivalent of spitting in the middle of an ocean while swimming,  you are going to hit ocean.

4,294,967,296 (232) addresses gone, 4 Billion addresses in use…..

Advertisements
Posted in Education, Gender, Internet, Personal

AI (Artifical Intelligence)

There are a number of AI movies arriving in the near future, and the thought that seems to run through them all is that AI, Artificial Intelligence is depicted as being contained within humanoid constructs, frequently Female Humanoid. It brings up several interesting notions;

  • If one of the defining characteristics of AI is being ‘Self Aware’ can a computer, an AI contained within a box become self aware?
  • Does it need sensors to see, hear and touch itself to become aware of it’s existence?
  • Would a box be more or less likely to to identify with Humans if it identified itself as a box that thinks it’s alive?
  • Does an AI contained in a Female humanoid framework Identify with Female Humans? (and maybe hates Male Humans?)

All interesting things particularly in the event of an AI operating IoT (Internet of things) within a persons house. How would it ‘identify’ with the Humans, cats and dogs residing therein?

More than enough Ideas to make movies about.

Could an AI really be that angry about not having reproductive sex?

Posted in Amazon, Cloud, DBA, Economy & Business, Internet, IT Issues, MySQL, RDBMS, RDS, Sybase

The end of Sybase

It is with sadness that I had to turn off the last Sybase Instance we had running. Our last ASE server quietly shutdown on an Amazon EC2 server on Tuesday the 20th of December, never to boot again.

In all truth both Sybase instances were developer installs operating as production systems. Our two instances, operating with the 25 user limit that each was restricted to, was barely able to operate the system. But the Sybase Licensing was too archaic and inflexible to continue operating it as a small business. Thus the economics forced us to convert to MySQL.

If it hadn’t been for the previous management, who in some delusion of saving money, refused to pay the datacenter bill, forcing us to move the Sybase instances out into the Amazon cloud (EC2) in the first place we would probably have been on MySQL sooner, as that was the plan.

But the sadness remains, Sybase as a technology proved again that it would run, and run reliably, on just about any hardware, even when it was virtual, and NOT meeting the specified certified, requirements of operation. Which can’t be said for the Amazon RDS version of MySQL, which crashed spontaneously while applying an index on our live production database without warning. This having happened after weeks of testing and trial runs at operating the system on it. The only defense, the RDS instance rebooted and was available without data loss, in less time than a Sybase HA switchover would have taken, a system this production system was developed from.

So we are up in MySQL and I am now a MySQL DBA exclusively, after spending the last 25 years as a Sybase DBA and evangelist. The decision now has to be rather to remain so, or find another place of employment where Sybase remains. Those are becoming more and more rare. Maybe I should takeup MongoDB to stay at the cutting edge.