WebProNews

Tag: Databases

  • IBM Acquires Cloud Database Company Cloudant

    IBM this week announced that it has officially completed its acquisition of Cloudant, a formerly private cloud database company based in Boston. The purchase price and other details of the transaction have not been disclosed.

    Cloudant provides database-as-a-service to developers and enterprise that need scalable database solutions implemented quickly. The company currently provides its services to clients that include mobile app developers, retail businesses, and companies in the financial services industry.

    Cloudant is also a contributor to the Apache CouchDB open source community. The company provides a JSON-based cloud service for web and mobile developers.

    “Our decision to join IBM marks a clear shift in the way modern software is built,” said Derek Schoettle, CEO of Cloudant. “A new generation of developers has grown up coding against web frameworks and cloud infrastructure. When Cloudant launched in 2010, we knew this next wave of innovation would be a core market for our service. Now in 2014, we’re seeing web development transition to the enterprise, and, as part of IBM, we couldn’t be in a better spot.”

    IBM will be folding Cloudant into its Information and Analytics Group. The company will integrate Cloudant technology into its big data and analytics, mobile, and cloud computing initiatives. Cloudant tech is already being used in IBM’s MobileFirst solutions and will soon be available through the company’s BlueMix platform.

    “With the acquisition of Cloudant, IBM is helping to fuel a new era of next generation mobile and web apps built on the cloud,” said Sean Poulley, VP for Databases & Data Warehousing at IBM. “Boosting IBM’s big data and analytics, cloud computing and mobile offerings, Cloudant’s open, cloud database service will bring entirely new levels of simplicity and scalability to developers.”

    Image via Cloudant

  • Police Tracking Your Every Move With License Plate Readers

    Police Tracking Your Every Move With License Plate Readers

    Privacy. It’s on everyone’s minds these days. A couple of months ago it was Apple and Google that were drawing the ire of consumers with the storing of location data. And of course, Facebook is always mentioned when people discuss their concerns about online privacy. But as technology gets better, and the tools used to capture information and the databases used to store and disseminate the information become more capable, the lines between online and offline privacy continue to blur.

    On that note, let’s say that you are having a Sunday afternoon picnic with your child. The weather’s good, you’ve been running around and playing – but now it’s time for lunch. You open up the cooler, only to discover that you’ve left a couple of the sandwiches in the car. The car’s just a few yards away, so you quickly run to grab the sandwiches.

    And in a split second, you look back to see that your child is gone. You catch a black sedan speeding away and you are barely able to catch the license plate. Because you caught that license plate, police are able to search a giant database of plate captures and track the movements of the kidnapper.

    A classic question: What is more important, public safety or personal freedom? What are you willing to sacrifice? Let us know in the comments.

    Ok, I know this whole scenario seems a little bit Without A Trace or Lifetime movie-esque, but the point is that police were able to use an ever-expanding database of data culled from license plate snapshots in order to generate real-time location information. That’s a reality, and it’s happening in our nation’s capital, among other places.

    The Washington Post is reporting that police in D.C. are beefing up the area covered by license plate cameras. More than 250 cameras in D.C. and its suburbs are constantly hard at work, grabbing license plate numbers and sticking them into databases. The police aren’t exactly doing this quietly, but it’s being done with “virtually no public debate.”

    The highest concentration of these plate readers in the entire nation exists in D.C. (one reader per square mile), so that means that District police are building the biggest location database based on license plates in the whole country.

    Let’s take a brief look at these license plate readers.

    First, these are apparently different types of cameras than the cameras cities have been affixing near stoplights and other places to catch people running red lights or speeding – the “here’s a ticket 2 weeks later in the mail” cameras.

    These plate readers cost about $20,000 each and can snatch images of numbers and letters on cars traveling nearly 150 mph and across four lanes of traffic. These plate readers in D.C. take 1,800 images per minute, every one of which is stored in a database.

    Basically, these plate readers have made it possible for police to track everyone’s movements as they move across the city.

    These plate readers and the subsequent database of image captures has tipped the privacy concerns of some – notably the American Civil Liberties Union. One of their main concerns is naturally the privacy implications.

    In the District, laws are in place that limit the amount of time that surveillance camera footage can be kept. The images must be dumped after 10 days, unless there is an actual investigatory reason to keep them. But right now, there is nothing keeping data from the plate readers from being stored for years.

    The ACLU says that this database is storing the location data of innocent people. And they are right. The plate readers are casting an all-inclusive net, grabbing license plate numbers indiscriminately.

    Clearly this technology is rapidly approaching the point where it could be used to reconstruct the entire movements of any individual vehicle. As we have argued in the context of GPS tracking that level of intrusion on private life is something that the police should not be able to engage in without a warrant.

    Let’s think back to the slightly-stylized child abduction scene from the beginning of this article. Maybe that seems a bit far-fetched, but the reality of the situation is that the plate reader database has helped police. According to the D.C. police department, they make an arrest a day with the help of the plate readers. In a four month period this year, they also found 51 stolen cars.

    And although our child abduction story above might seem unrealistic, the possibilities are there for the plate readers to help in truly significant ways. Police could track cars to and from murder scenes or use it to identify players in organized crime circles like sex trafficking – by logging which cars travel between certain locations.

    But the fact that the technology is beneficial or could be beneficial in terms of law enforcement does not assuage concerns of a “surveillance society” becoming the norm in the U.S. It’s a classic argument that pits personal liberties against security and safety. Just how much of your freedom are you able to give up to feel safer? This is a crucial debate that we’ve seen play out most recently after 9/11 with the Patriot Act.

    The ACLU channels Minority Report to discuss preemptive law enforcement:

    Of course, if the police track all of us all the time, there is no doubt that will help to solve some crimes — just as it would no doubt help solve some crimes if they could read everybody’s e-mail and install cameras in everybody’s homes. But in a free society, we don’t let the police watch over us just because we might do something wrong. That is not the balance struck by our Constitution and is not the balance we should strike in our policymaking.

    Obviously, the plate readers are a valuable tool for the police, and there are an abundance of situations where one could imagine the searchable database of plate captures to be extremely useful. But are those plate readers building up a database that’s just a little too full of innocent people’s location information for your liking?

    If this kind of thing is to proliferate (both in D.C. and across the country), it is argued that it needs to see the light of day. Basically, society should have time to debate its merits and discuss their concerns. “The police should not be able to run out and buy a new technology and put it in place before anybody realizes what’s going on,” says Jay Stanley of the ACLU’s Privacy and Technology Program.

    What do you think about the expansion of the plate reader technology? Do the benefits outweigh the privacy and personal freedom concerns? Or is this an example of big brother yielding too much power with the ability to catalog this data without warrants? Let us know in the comments.

  • Cost Effectiveness of Amazon RDS Pay-Per-Usage Software Pricing

    Established software vendors face a difficult balancing act between meeting customer demands for pay-per-usage cloud pricing models while guarding against revenue erosion on traditionally priced offerings. If Amazon’s price for Oracle Database on RDS becomes the norm for price discrimination between traditional and per-per-usage licenses, IT buyers could find themselves paying over a 100 percent premium for the flexibility of pay-per-usage pricing.

    Note, I am only using Oracle as an example here because the pricing of Amazon RDS for Oracle Database is public. This post intends to make no judgments on Amazon or Oracle’s price points whatsoever.

    Pay-per-use software pricing limited to entry level product
    Amazon RDS for Oracle Database offers two price models, “License Included” or “Bring Your Own License (BYOL)”. The License Included metric is fancy terminology for pay-per-usage, and includes the cost of the software, including Oracle Database, underlying hardware resources and Amazon RDS management.

    Three editions of Oracle Database are offered by Amazon, Standard Edition One (SE1), Standard Edition (SE) and Enterprise Edition (EE), listed in order of lowest to highest functionality.

    It’s important to note that pay-per-use pricing is only offered on the lowest function edition, namely, Oracle Database SE1. This should not be a surprise as Oracle, like other established vendors, is still experimenting with pay-per-usage pricing models. Customers can also run Standard Edition One using a BYOL model. This fact, along with Oracle’s list pricing, helps us do some quick and interesting calculations.

    Oracle Database SE1 software price-per-hour ranges between $0.05 to $0.80
    The License Included and BYOL prices both include the cost of the underlying hardware resources, OS and Amazon RDS management. The only difference between the two options is the price of the Oracle Database software license.

    This allows us to calculate the per hour cost of Oracle Database Standard Edition One as follows:

    The Oracle list price for Oracle Database SE1 is $5,800 plus 22 percent, or $1,276 for software update, support and maintenance. Like most enterprise software, customers could expect a discount between 25 to 85 percent. For lower priced software like Oracle Database SE1, let’s assume a 50 percent discount. Although, most customers buying Oracle software are encouraged to enter into Unlimited License Agreements (ULAs) which frequently offer discounts at the higher end of the spectrum.

    All told, Oracle Database SE1 after a 50 percent discount would cost a customer $3,538 (($5,800 + $1,276) x 50%) for 1 year or $4,814 ($5,800 + $1,276 + $1,276 + $1,276) x 50%) for 3 years on a single socket quad core machine like this low end Dell server. Note that Oracle doesn’t use their typical processor core factor pricing methodology for products identified as Standard Edition or Standard Edition One as they are targeted at lower performance servers.

    A single socket quad core machine would offer the performance of somewhere between the Amazon “Double Extra Large DB Instance” and the “Quadruple Extra Large DB Instance”.

    Consider the long term costs of per-per-usage

    Using “Double Extra Large DB Instance” pricing, with our calculated cost an Oracle Database SE1 software license on Amazon of $0.40/hr, we can calculate a 1 year cost of $3,504 and a 3 year cost of $10,512. These figures represent a 1 percent lower and 118 % higher cost of using Amazon’s per-per-usage offering versus licensing Oracle Database SE1 through Oracle for on premises deployment or a BYOL for deployment on Amazon RDS.

    There are obviously multiple caveats to consider, like the ability to get lower or higher discounts from Oracle, or comparing with the “Quadruple Extra Large DB Instance” price point.

    A customer that is unable to get a 50 percent discount from Oracle could save licensing costs by using Amazon’s pay-per-usage offering for Oracle Database SE1. For instance, with only a 25 percent discount from Oracle, the customer could save up to 34 percent on a 1 year basis, but stands to pay an extra 46 percent a 3 year basis.

    Comparing the cost of Oracle Database SE1 using traditional licensing on premises with Amazon’s pricing through RDS, it appears that customers should look hard at Amazon’s per-per-usage offering for up to a 1 year term, but stick with Oracle’s traditional pricing model if the software is going to be used for the typical 3 to 5 year period that companies like to amortize costs over.

    The obvious rebuttal to the above calculations would be that a customer electing for a pay-per-usage model would not necessarily run for 24 hours a day for a full year. While this is true, buyers should understand the long term cost implications before making short term decisions.

    Originally published on rand($thoughts);