The software industry is truly brutal. Competition is fierce and technology is evolving faster every day. And every few years there is a need to completely rewrite your software and that is nothing less then a life threatening endeavor.
When it comes to in-memory computing, shrinking means acceleration. Imagine an app that intensively reads and updates in-memory data. Can you make it run faster by doing more CPU work? The answer is positive and the solution is, indeed, captivating.
Technology comes before revolution. Always. And while not always obvious when first introduced, the importance of truly novel technology is not something reserved for tech geeks; in fact, it is and has always been vital for the evolution of the human race. […]
Data processing is ubiquitous (this should be a surprise to exactly no one). From money transfers to your phone contacts being stored in the cloud, the average consumer unknowingly benefits from data processing daily. […]
Our team has been busy preparing for the NoSQL Now! show, and we’re so excited about it that we decided to give you a sneak preview of what we have planned for our speaking session.
Our founder, Joachim Wester, has a strong background in building data management solutions for the largest Scandinavian enterprises. He was doing eventual consistency long before it ever became mainstream, and he knows what’s wrong with it.
Recently, I’ve noticed that Web Components has become the subject of many speaking sessions at IT and developer events – most notably InfoShare 2014 and Front Trends 2014. What was once a trend discussed in just a few online forums is now becoming part of every technology event!
In April, Jeff Cotrupe of Frost & Sullivan’s Stratecast practice featured Starcounter and its patented VMDBMS technology in his report, “The Real-time is Now for Big Data to Pass the ACID Test- Could this be a Turning Point.” The report looks at three main challenges that organizations are facing as they move to a Big Data-driven future, and discusses the viability of Starcounter as a solution […]
This article is homage to jQuery – a library that once was a great boost for the productivity of thousands of web developers around the world. In the near future, the benefit of using it will drop as web developers start switching to the web standards, including Web Components. […]
This month, IDC’s Carl Olofson highlighted Gekås Ullared’s use of our database technology in his case study, “Sweden Turns to Gekås Ullared for Bargains; Gekås Turns to Starcounter for Database Power”. […]
Web Components is an umbrella term for the set of upcoming standards for web development (see the W3C Web Components page). Each on its own is a useful contribution to the current toolset for a web developer. When used together, they form a completely new paradigm of how web applications are created. […]
In part one of this two-part blog post, we explored a few things you should consider when choosing a new database, including the purpose of the application, true consistency, and high performance. Part two touches on four additional factors you should keep in mind during your selection process.
4) Is your data safe?
When your data is written, will it be secured for the future? Is there a delay between committing a transaction and securing the information? If the application cannot be restored following a power loss to the absolute latest committed transaction, it is not considered to have durability (the “D” in ACID). […]
When you look at the database market, it’s a virtual jungle out there. Those of us in the industry 15 years ago can look back and remember when we only had the option to use a relational database from Sybase, ORACLE, Microsoft or IBM. That was pretty much it if you were planning to build a new complex application with persistent storage.
Nowadays, the number of options is absolutely brilliant, but this also means you need to do your homework. I found a great visualization of the database market landscape by 451 Research. The similarity to the London underground map is striking!
Image from 451 Research, Matt Aslett
If you don’t do your research before choosing a database, you could end up disappointed. So exactly what are the main issues you should consider? For part one of this two-part blog post, I will explore three factors including the purpose of the application, true consistency, and high performance. […]
Starcounter has been chosen as one of 22 companies participating in “Innovationsbrons” program Market Access Silicon Valley.
Startup mogul Ola Ahlvarsson lists four Stockholm based ICT companies that investors should keep a close eye on.
Starcounter, Tobii, Klarna and Rebtel.
Starcounter’s will exhibit at the NoSQL Now! show in San José in August 21-23. Please come visit us in our boot!
I like the philosophy of the REST style, but I also have a major beef with it. Before getting in to that, let’s first define what REST is. Right now, there are two flavors of REST. One is the real one, as described by Dr. Fielding in his dissertation. The other one is what is merely any web service that uses HTTP, URIs and Json as its mechanisms. […]
Starcounter’s CTO Peter Idestam-Almquist will present “NewSQL Database for New Real-time Applications” at NoSQL Matters Conferende ín Köln Germany 2012 May 30. Read more about the show and the Starcounter presentation.
If you have a successful application and it relies upon persistent data then data storage will probably become your bottleneck. There are two main strategies for scaling an application: vertical scaling and horizontal scaling.
Horizontal scaling means distributing the data over several database nodes. According to the CAP theorem you can only have two out of consistency, availability and partioning tolerance. Since horizontal scaling is based on partitioning and availability is required for online applications, you typically give up consistency. […]
The latest and greatest from Microsoft when it comes to web development is Microsoft MVC. Although the acronym is new to many young web developers, MVC was actually quite popular in object oriented UI development in the early eithies. Back then, the best implementation did not only have one Model, they had two. The domain model was the business objects and the application model has used to drive the views. The MVC tools used today have used the MVC acronym carelessly. So carelessly in fact, that when the application model is finaly reintroduced, the vendors feel that they need totaly new acronyms for this beatiful pattern. So say hello to MVVM (Microsoft), MDV (Google) and also to MMVC, MVP and what have you. […]
Imagine if Toyota trying to forbid anyone to publish information on how fast it is from 0-100 km/h (0-62 mph) or how much petrol it consumes per mile. Consumer activists and governments would not have it.
But hear this! Some database engine vendors actually do just that! They forbid the user to publish any benchmarks what so ever. The way they’ve managed to do it is actually a quite cunningly worked out construction in their licensing. The scheme goes like this: […]
The web browser is taking a giant leap forward. The average user has yet to see the difference it will bring, but on every smartphone and desktop, there is a roaring tiger waiting to come out of its cage. The most important change is that the biggest player, Microsoft, had to change its stance.
If software runs on your desktop operating system and you own 90% of the browser market, you can be excused for not wanting to drive your users away from the desktop to run their apps. But when you fall below 50% with a negative trend, and people are fleeing to smartphones and tablets you’ve got to act. And this is where Microsoft shows its strategic skills. […]
# The real time web
The countdown has begun for the real time web. The technology is out on iPhones, Androids and desktop users having Firefox or Google Chrome. Now we are holding our breaths for Internet Explorer 10, the final piece of the puzzle. What I’m talking about, of course, is WebSockets. Putting the technological details aside, WebSockets means that the dead pages of the web can come alive. […]
Software people are bound by trends and tradition. Although some of us wants to think of ourselves as forward thinking and open minded, we are no better than our peers. You can pick a point of time in history at random and still rest assured that most buzzwords du jour sounds corny ten years later. And if you were amongst its loud voiced supporters, you would probably turn red hearing yourself advocate the latest-and-greatest.
At the time the trendy technology sounded so right, so new and so fresh. But just a few years later, the very same concepts will have seize /*seize?*/ to be in the center of attention. Some will be part of our everyday life and some will have left their mark as basis for the next thing and some will simply die. If we were there, as visitors from the future, we would tell the advocates of WAP, Enterprise Java Beans and ActiveX components that they might as well tone it down. […]
Applications that Create, Read, Update and Delete are should be so simple, and yet, they create so much headache. Writing a local application for a single user is simple. Writing a scalable multiuser system is hard.
If you architect applications with many users, your bottleneck is ultimately going to boil down to management of shared state.
Static data or data not requiring synchronization/transactions can be replicated cheaply across many small commodity servers. In resent years, many database solutions have come to handle this nicely (especially the newer NoSQL* databases that were designed for horizontal scaling from the get go). […]