NEC POLLS

What is the most important goal of using Big Data in your organization?
 

User Menu

Forum Users Online

Now 107 guests online

Font Size Changer

More than a day canada soltamox that old.
    
 

Straight Talk

Key Value Stores are perhaps the most common form of NoSQL and NewSQL databases.  They consist of (surprise!) keys and values and are built from the ground up to store and retrieve these values as fast as possible.  For this reason, a KVS is considered an excellent way to store and retrieve information for high-traffic web sites and other high-performance content, but not the greatest for transaction-driven projects.   According to DB-Engines, key value stores are one of the more popular non-RDBMS databases in use.

Structurally, KVS are the most straightforward of the NoSQL databases and this basic underlying factor accounts largely for why they are so mind-bogglingly fast.  The beauty of a KVS is its simplicity.  Instead of worrying about complex schema and data relationships (as with a traditional RDBMS), a KVS just has to store and retrieve values linked to a key.  The most commonly implemented KVSs include Redis, Riak, and VoldemortNEC’s IERS is built on top KVS with many added enhancements.

It’s easier to understand a KVS if you first look at a traditional RDBMS.  Think of this as a structured and table-based database.  For example, if you’re working with employee data, you’d have a table with columns for each field you wanted to track and a row for each user.  It would look something like this:

ID

First Name

Last Name

1

Homer

Simpson

2

Marge

Bouvier

3

Herschel

Krustofsky

The table approach works well if you have a reasonable number, a few dozen to a few thousand, of people to track.  It also works well if you can do your queries off-line where speed isn’t an issue, and can do your batch processing for reporting at off hours because those reports will take a considerable amount of time.

However, in the big data world we don’t have the luxury of running queries and reports during off-hours.  Whatever it is, in the big data world we need it now.  Not only that, the traditional table shown above may become a big management mess when it’s too big to fit on a single server. Taking the example to a KVS, imagine that you’ve got users instead of employees.  Now you’re talking about millions of records instead of thousands, and they need to be available quickly from around the world 24/7.  When a user logs in, he wants to be able to have instant access to his account.  Plus, not every user record has every bit of information as every other record; some users may provide their phone numbers, some may not.  Each record potentially has a different length and different values.

To store and retrieve this kind of data quickly, you generate a key for each record and then store whatever fields (what would have been columns in the table above) are available.  Each field is comprised of a data name and the data itself.  If you don’t have a particular piece of data, instead of leaving an empty cell in a table you simply don’t store the data name / data combination.

Let’s take a look:

Key: 1

ID: HS

First Name: Homer


Key: 2

Email: This e-mail address is being protected from spambots. You need JavaScript enabled to view it

City: Springfield

Age: 34


Key: 3

Twitter ID: @hkrustofsky

First Name: Herschel

Occupation: Clown

As you can see, users can log in using ID, email, or Twitter ID.  This simply wouldn’t have been possible using a traditional table style RDBMS.  Also, queries need to be built around keys because there are no field (or column) names.  There’s no need to pull data from multiple tables, reformat it and import it into another table just so users with different information stored can log in.

NEC’s IERS takes advantage of the straightforward nature of a KVS.  I blogged about this a few weeks ago when I posted coverage of my interview with Atsushi Kitazawa, the “father” of IERS.  Due to the nature of a storing multiple values associated with a unique key, distributed KVS performance is predictable.  A KVS is usually partitioned to run on multiple nodes.  Because each key is unique, all values associated with a key, regardless of where the values are physically located, are equally accessible. 

So there you have it, an explanation of KVS’s and how they work.  While a KVS forms the foundation of NEC’s IERS, there are plenty of enhancements that take IERS above and beyond what the average KVS is capable of.  In particular, IERS provides a high-performance and consistent environment with transparent scaling for transactions.  My next posting will discuss these advantages and how to make the best use of them when developing for IERS.

To learn more about NEC’s IER’S solution visit:  http://goo.gl/TnFkbR

    *Matt Sarrel is a leading tech analyst and writer providing guest content for NEC.


( 0 Votes )

NEC Summer Reading List

 

Recently the Irving (TX) Public Library reported a 35% increase in its summer reading program from a year ago. This is good news for kiddos wanting to keep their minds active over the summer break. So that you can also keep your mind active, and because we did not want you to feel left out, we’ve compiled our own summer list of powerful informational topics. You can read or listen to great content and bone up on all things innovative, technical and positive for the society! Check out our sessions:

Solutions for Society

Solutions that make things better for society as a whole. Think about how much safer we are by being able to identify bad guys quickly with our NeoFace® facial recognition solutions. Many innovations positively impact society, from big data to healthcare innovation. Check it out…

From NECToday

What Do Intel’s Youngest Intern and NEC Have in Common?

Joey Hudy is the youngest intern in Intel history. At 16 years old, he has achieved multiple accomplishments including a solar-powered computer submitted at a recent science fair. His personal credo – Don’t be bored, make something – is a commitment from NEC as well.

Biometrics Can Improve Customer Experiences

According to a report from research firm Frost & Sullivan, biometrics is just beginning to gain recognition as a viable solution for customer experience in the retail and hospitality industries.

The biometric market is expected to be worth $6.2 billion by the year 2019, primarily due to the continued adoption of the technology for applications beyond the law enforcement and government arenas. For example, the banking industry has found biometric facial recognition to be quite useful in ATMs.

Big Data to the Rescue

What do Lady Gaga, the FIFA World Cup committee, and major communication companies have in common? Big data! Check out these real-life use cases to learn how big data significantly impacts the lives of just about everyone.

Healthcare Innovation for Improved Patient Experience

The primary objective of any healthcare provider is to focus on the patient. Whether it's a private practice or a large medical conglomeration, the healthcare system needs improved patient communication in order to ensure positive patient experiences.

From NECAM Soundcloud Channel

JPS Heath Network

JPS Health Network is the public healthcare system for Tarrant County and surrounding areas in Texas. Its flagship facility, JPS Hospital, is in Fort Worth and is the only Level-I Trauma Center in the county. The network also includes 42 primary and specialty clinics and health centers throughout the county to serve its population of approximately 2 million citizens. NEC helped JPS upgrade its communications platform to help staff and doctors deliver quality care to its patients.

Commonwealth of Pennsylvania – Justice Network

The Pennsylvania Justice Network (JNET) is a collaborative effort of 16 state agencies to build a secure, integrated justice system that promotes information sharing through the use of its applications, services, architecture, outreach and training.

Case Study: Children’s Hospital of Orange County

Named one of the best children’s hospitals by U.S. News & World Report (2013-2014), CHOC is exclusively committed to the health and well-being of children through clinical expertise, advocacy, outreach and research that brings advanced treatment to pediatric patients. 

Software-Defined Everything

The “Internet of Everything” taken to the next logical step – software-defined so it’s proactive, interactive and positive for companies who want to save time, money and improve productivity. Learn more about next-gen systems…

From NECToday

Continuous Availability at an Affordable Cost for Today’s Business

For IT organizations with mission-critical data, as well as large retailers needing to maintain and access data quickly, the requirements for server uptime and processing are even more important. Trying to achieve five nines (99.999%) of uptime is feasible in a clustered data center environment, but often these organizations are better served through the implementation of a fault tolerant (FT) server.

An Introduction to IERS and NoSQL / New SQL

NEC Corporation of America recently announced the general availability in North America of the InfoFrame Elastic Relational Store, a high-performance database built for high availability and flexible scalability.  IERS is a key value store that provides high-speed transaction processing and SQL (structured query language) capabilities through a JDBC/ODBC interface.  

An Interview with Atsushi Kitazawa of NEC Japan, the “Father” of IERS

Everything you wanted to know about IERS, from its position in the world of next-generation databases to its design goals, architecture, and prominent use cases.

From NECAM Soundcloud Channel

The Path to Five 9s of Availability for SQL Server

Get an overview of the different SQL Server high availability technologies from the lowest to the highest levels of availability.

Stay In the Know While On the Go

Mobility is only becoming more prevalent, so check out these great options to learn more about how to keep your mobile workforce productive, secure and well, mobile! Explore on the go…

From NECToday

Under the Sea…with Internet?

Can you imagine a world where ANYTHING is possible? Science fiction movies have depicted it: people living on the moon, on a planet, or under the sea. But now, are we coming closer to fantasy becoming a reality? Perhaps so!

How to Stay ‘Mobile’ During a Severe Weather Event

Enabling employees to do their jobs even when they can’t get into the office keeps them safe during dangerous travel conditions, but it also means not losing employee productivity over the course of the weather event.

Get the Best of All Worlds with In-Store Mobile

In-store mobility is the most efficient and accurate way to create the type of retail experience a consumer expects. Plus, it supports associates in providing a rapid response to a shopper’s needs, ensuring that the sale goes to your retail establishment. To understand the power of in-store mobile, first let’s understand the current consumer shopping behavior.

From NECAM Soundcloud Channel

Case Study: Schenectady City School District

Schenectady City School District (SCSD) is located 12 miles from Albany, New York. The district offers hundreds of courses and programs to nearly 10,000 students throughout the city of Schenectady, and has more National Board Certified Teachers (NBCT) than any other district in the state, with the exception of New York City.

It’s In the Cloud

Isn’t everything? Truth is that cloud solutions have significant practical applications for most businesses, if you understand how to apply them correctly. Do you need a hybrid, cloud or on-premises solution? Find out the answer to that question and more with these sessions:

From NECToday

Is Your Company Seeking Business Agility? Uncovering the Business Value of SDN

Hear first-hand SDN thought leaders from NEC, IBM and featured analyst firm Gartner Research talk about the business benefits of software-defined networking.

NEC Teams with Microsoft for Flexible, Open, Standards-based SDN for the Cloud

Mike Schutz, general manager of Microsoft Product Marketing for the Server and Tools Group, talks about the collaboration between these strategic partners and the benefits customers can expect in this new video.

Unified Communications: As-a-Service vs. On-Premises – What’s Best for You?

Simplifying communication and collaboration is the hallmark of UC and UCaaS. The good news is you don’t have to choose.

ONF Honors NEC as First Vendor to Certify for OpenFlow 1.0 Conformance

The Open Networking Foundation (ONF), a user-driven organization focused on the promotion and adoption of Software-defined Networking (SDN) through open standards development, has awarded NEC Corporation (NEC) with the first Certificate of Conformance offered through the ONF’s OpenFlow Conformance Testing Program. A Certificate of Conformance from ONF is the highest level of assurance available in the market today to confirm OpenFlow specification compliance.

NEC Collaborates with Microsoft to Transform the Data Center with Software-Defined Networking

Microsoft and NEC joint customers will command new levels of IT flexibility and automation with dynamic management and allocation of pooled network resources, as well as their compute and storage pools, all from a central point of control.

From NECAM Soundcloud Channel

Webinar: Real-Life SDN Use Cases

This webinar, Real-Life SDN Use Cases, features noted network experts Ivan Peplnjak of iosHints and NEC's network architect Samrat Ganguly. They present real examples of OpenFlow-based SDN at work, and use the NEC ProgrammableFlow® Networking Suite as the market leading vehicle to achieve transformative results.

There is plenty of other great content at your fingertips. Simply check out any one of our content channels and enjoy your own personalized summer reading program!

www.NECToday.com
http://www.youtube.com/interactivenec 
https://twitter.com/nec 
http://www.facebook.com/NECAmerica 
http://soundcloud.com/necam
https://www.linkedin.com/company/nec-corporation-of-america
 


( 0 Votes )

In the July issue of Business Solutions Annual Guide to POS & Payment Processing, NEC’s TWINPOS G5 point-of-sale (POS) solution was featured in a product review of all-in-one POS terminals. The criteria:

  • Submit a 15-inch, all-in-one POS unit
  • Must be equipped with 2GB of RAM
  • Costs around $1,300 to a dealer (but not exceeding $1,400)

NEC scored well against its competitors, and its POS solution was recommended for use in all categories, including grocery, general and specialty retail. Below are key features that were highlighted in the review:
Processor Speed/Functionality

  • NEC’s POS ranked in the top three for processor and network utilization, largely because of the dual-core processor.

Display/Finish

  • According to the review, the NEC terminal had the “most impressive display,” specifically when it came to resolution and color presentation.

Repair Ease/Time

  • NEC’s solution ranked as one of the top two POS systems that were the easiest to access for repairs.

To learn more about NEC’s retail solutions, visit www.necam.com/retail for more information.


( 0 Votes )

 

Can you imagine a world where ANYTHING is possible? Science fiction movies have depicted it: people living on the moon, on a planet, or under the sea. But now, are we coming closer to fantasy becoming a reality? Perhaps so!

Case in point – recently Fabien Cousteau, the grandson of the late Jacques Cousteau, famed underwater photographer and scientific researcher/oceanographer, announced he will make his home under the sea for 31 days, which would outdo his famous grandfather's record of 30 days, which was set nearly 50 years ago.

 Stay connected with NEC solutions

But the challenge is not just some "Harry Houdini" personal challenge the 46-year-old wants to take on. Cousteau will be there will a full team of scientific researchers to study the underwater environment, in an attempt to understand its challenges and unique issues.

When interviewed, the younger Cousteau stated that there would be a number of challenges, both physically and psychologically, but that "the backyard will be infinite."

But perhaps the most interesting thing about this scenario is the fact that, with all of the new technologies available, Cousteau will still be connected to the world through the use of modern communications systems now available to a global market.

NEC’s UNIVERGE 3C™ UC system enables people to communicate “anywhere, anytime from any device.” 3C handles the seamless integration of multiple devices and platforms, and is truly an all-in-one solution to communications in the 21st century.

Some of the features of this innovative technology include:

A software-based solution that allows integration of multiple media aspects, communication, and collaboration is a Godsend for any industry  that needs a way to communicate at different times or even across different time zones. The built-in recording capability is a big plus, as it allows people to record and document events at a moment's notice, no matter where they are located.

It also offers some security, and peace of mind, that, should something go wrong, one could easily alert people from the outside world without having to go to another location.

‘COMMUNICATE ANYWHERE, ANYTIME – UNDER WATER, ACROSS LAND OR… ACROSS THE LOBBY’

The hospitality industry embraces the ease of use, mobility and robust capabilities available with this technology and others. The average traveler is constantly connected, consistently mobile and expects to be plugged in all the time. Or at least have the option to stay in contact while on the move.

Many hotels and motels, resorts, and other locations are starting to implement this technology by offering not only wireless, but integrated communications solutions that allow you access to your virtual desktop from your mobile devices and other portals through the use of Desktop-as-a-Service (DaaS)and 3C solutions. 

DaaS provides access to your desktop from the cloud, no matter your location.  It is a virtual solution to access information and functionality without physically being at the location where the data resides. NEC's DaaS offering creates a secure gateway between the individual’s location and the virtual desktop, then passes the information back to the person, no matter where he is.

Some newer hotels even have ways for guests to control the room technology without ever leaving their beds, such as thermostats and cooling systems, lights, and even security systems. The ability for guests to interact with technology in their room seems almost space age – but is already here.

THE JETSONS ARRIVE

There's no doubt the world is changing and new technologies enable amazing things which would only have been dreamt of in the past. So, when Jane and George check into a hotel, instead of having to fumble around for their ID and their credit card, a facial recognition solution, such as NEC’s VIP guest recognition system, NeoFace® Watch, will recognize them as they walk up to the front desk. They can use an app to check into their room and may have the option to pay their bill by scanning their fingerprint at the checkout area.  Once inside their room, our couple will be able to control the thermostat, security system, and lights with only a click, while ordering room service with another app on their smart devices. This technology is here and it is an exciting time for anyone wanting to enjoy all of the amenities of home while away.

The future technology available for hotels and other hospitality venues will be on display at the HITEC technology show in Los Angeles from June 23 through 26. We’ll be there showcasing some of these amazing innovations, so please stop by NEC’s booth If you cannot attend, please visit our hospitality solutions page to learn more about technology that helps make your guests more comfortable, and your staff more efficient.

 

 

                                 


( 0 Votes )

Everything you wanted to know about IERS, from its position in the world of next-generation databases to its design goals, architecture, and prominent use cases.

I recently got the chance to talk to Atsushi Kitazawa, chief engineer at NEC Corporation, about the company’s new InfoFrame Elastic Relational Store (IERS) database.    I enjoyed the discussion with Kitazawa-san immensely – he has an ability to seamlessly flow from a deep technical point to a higher-level business point that made our talk especially informative.

Matt Sarrel (MS): Where did the idea for IERS come from?

Atsushi Kitazawa (AK): We decided to build IERS on top of NEC's micro-sharding technology in 2011. The reason is that all of the cloud players see scalability and consistency as major features and we wanted to build a product with both. Google published the Google File System implementation in 2003 and then they published Bigtable (KVS) in 2006. Amazon also published Amazon Dynamo (KVS) in 2007. NEC published our CloudDB vision paper in 2009, which helped us to establish the architecture of a key value store under the database umbrella. In 2011, Facebook published improved performance of Apache Hadoop and Google published the method of transaction processing on top of BigTable called Megastore BigTable. Those players looked at scalability and then consistency. By 2011 they had both.

A KVS is well-suited for building a scalable system. The performance has to be predictable under increasing and changing workloads. At the beginning, all the cloud players were using replication in order to increase performance, but they hit some walls because of the unpredictability of caching. You cannot cache everything. So they moved to a caching and sharding architecture so you can partition data to multiple servers in order to increase caching in memory. And then the problem here is that it is not so easy to shard a database in a consistent manner. This is the problem of deep partitioning. You can see the partitioning or sharding in the beginning—it is not so difficult--but dynamic partitioning and sharding is very difficult. The end goal of many projects was to provide a distributed KVS. The requirement of a KVS is predictability of performance under whatever workload we have.

MS:  Why is a KVS is better? 

AK: The most important thing about a KVS is that we can move part of the data from one node to another in order to balance performance. Typically, the implementation of a KVS relies on small partitions that can be moved between nodes. This is very difficult when you consider all of the nodes included in a relational database or any database for that matter. In a KVS, everything is built on the key value so we can track where data resides.

Going back to the evolution of database products, Facebook developed Cassandra on its own because it needed it. It had to move part of the application from Cassandra to HBase but had to improve HBase first. Facebook reported in a paper the reason why it had to use HBase is that it need consistency in order to implement its messaging application. The messaging application, made available in 2011, enabled users to manage a single inbox for various messages including chats and Tweets. This totals 15 billion messages from 350 million members every month and 120 billion chats between 300 million members. Then Facebook wanted to add consistency on top of performance because of the increased number of messages delivered.

On the other hand, Google added a transactional layer on top of its BigTable KVS. It did this for the app engine that is used by many users concurrently. The transactional layer allowed users to write their application code.  Google also developed Caffeine for near-real-time index processing and HRD (High Replication Datastore) for OLTP systems such as AppEngine to use.

Those are the trends that cloud players illustrated when NEC was deciding to enter this market. At NEC we developed our own proprietary database for mainframe moret han 30 years ago. Incidentally, I was on that team. We didn't extend our reach to Unix or Windows so we didn't have a database product for those platforms. In 2005, we decided to develop our own in-memory database and made it available in Japan. This is TAM or transactional in-memory database. We added the ability to process more queries by adding a columnar database called DataBooster in 2007. Now we have in-memory databases for transactions and queries. In 2010, we successfully released and deployed the in-memory database for a large Japanese customer. As our North America research team released the CloudDB paper, we merged the technologies together to become IERS.

We felt that if we could develop everything on top of a KVS, then it would be scalable. That is a core concept of IERS.

MS:  What were the design goals of IERS?  Could you describe how those goals are met by the system’s architecture?

AK: Regarding our architecture, the transaction nodes implement intelligent logs with in-memory database to facilitate transaction processing. The difference between IERS and most databases is that IERS is a log system machine. IERS does not have any cache (read, dirty, write) and this means we don't have to synchronize cache in the usual manner. We just record all the changes to the transactional server in time order fashion and then synchronize the changes in batches to other data pods over IERS, which are database servers. The result is that the KVS only maintains committed changes.

We do have a cache, but it is a read-only cache, not the typical database cache. The only data the cache maintains is for reads from the query server. We do not need to be concerned with cache coherency. The transaction server itself is an in-memory database. We record every change on the transaction server and we replicate across at least three nodes. The major difference between IERS and other databases is the method of data propagation. Our technology allows the query server, accessible via SQL, to see a consistent view even though we have separate read and write cache. If you do not care much about consistency, then you can rely on the storage server's cache. The storage server consists of the data previously transferred from the transaction server. If you consider the consistency between each record or each table, then you should read from the transaction server so that we maintain the entire consistency of the transaction.

The important point in terms of scalability is that both the KVS (storage) server and the transaction work as if they are KVS storage so we can maintain scalability as if the entire database is a KVS even though we have a transactional logging layer.

From a business point of view, there are users who are using a KVS such as Cassandra, which does not support consistency in a transactional manner. We want to see those users to extend their databases by adding another application. If they want a KVS that supports consistent transactions then we can help them. On the other hand, in Japan we see that some of our customers are trying to move their existing applications from RDBMS to a more scalable environment because of a rapid increase in their incoming traffic. In that case, they have their own SQL applications. Rewriting SQL for a KVS is very difficult if it doesn't support SQL. So we added a SQL layer that allows users to easily migrate existing applications from RDBMS to KVS.

MS: Is there a part of IERS' functionality or architecture that makes it unique?

AK:  From a customer point of view the difference is that IERS provides complete scalability and consistency. The key is the extent that we support the consistency and SQL to make it easier for customers to run their applications. We added a productivity layer on top of a pure scalable database. We can continue to improve the productivity layer. Typically, people have to compromise productivity to get scalability. Simply pursuing scalability isn't so difficult. Application database vendors focus on the productivity layer. Then they add scalability. Our direction is different. We first look at scalability. We built a completely scalable database. Then we added the productivity layer - security support, transactional support - without compromising scalability.

MS: What types of projects is IERS well-suited for?

AK: Messaging is one good application. If you want to store each message in transaction fashion (track if it goes out, if it's read, responded to, etc.) and require scalability, then this is a good application for IERS.

Another case is M2M because it requires scalability and there is usually a dramatic increase over time of the number of devices connected. The customer also has a requirement to maintain each device in transaction fashion. Each device has its own history that must be maintained in a consistent manner.

To learn more about NEC’s IER’S solution visit:  http://goo.gl/TnFkbR

    *Matt Sarrel is a leading tech analyst and writer providing guest content for NEC.


( 0 Votes )