Wednesday, September 06, 2017
Live Coding with AWS | Deep Learning Pt 2 - Sequence Modeling
Understanding the CAP Theorem
The CAP theorem is a tool used to makes system designers aware of the trade-offs while designing networked shared-data systems. CAP has influenced the design of many distributed data systems. It made designers aware of a wide range of tradeoffs to consider while designing distributed data systems. Over the years, the CAP theorem has been a widely misunderstood tool used to categorize databases. There is much misinformation floating around about CAP. Most blog posts on CAP are historical and possibly incorrect.
It is important to understand CAP so that you can identify the misinformation around it.
DBA Skills for Developers
In many smaller companies or departments, there is no dedicated DBA. In these cases, it falls on someone in the office to get to grips with the blackbox that is the database server, keep it running and dive in when the things go wrong. The objective of this article is to give non-data-focused developers a quick roundup of useful information and knowledge that will enable them to both solve some routine issues that come up and also help prepare for some in advance. This is not intended to be a very indepth article, rather its a quick read over coffee break that should give the reader some useful starting points. I would be delighted if any more experienced DBAs out there would like to comment and help expand the list. This article focuses specifically on MS SQL Server but the concepts should be useful for most relational database systems. I also attach some scripts as a download that I use to gather information on a system that you may find useful.
Core ConcernsA lot of projects start small, and over time the complexity increases. What was a good decision to start in the original design of a database or system may now be sub-optimal. Rather than putting solid fixes in place, for the sake of speed of development and 'getting things out the door', it is not uncommon to code around issues without digging-deep to find the problem and solve it. The following few items will give the new Developer DBA a head start in getting and keeping on top of things.
Beginner's Walkthrough: MongoDB and Java
This tutorial takes you through the basic process of installing MongoDB followed by simple CRUD application with Java and MongoDB.
What's in this tutorial?
Tuesday, September 05, 2017
Do You Really Need That SQL to Be Dynamic?
Dynamic SQL refers to a SQL statement that is constructed, parsed, and executed "dynamically" at run time (vs. "statically" at compile time).
It's very easy to write static SQL in PL/SQL program units (one of the great joys of working with this database programming language). It's also quite easy to implement dynamic SQL requirements in PL/SQL.
AWS KC Videos: How do I troubleshoot why my Auto Scale instances fail during scale-out deployments?
What Are the Keys to a Successful Database Strategy?
To gather insights on the state of databases today, and their future, we spoke to 27 executives at 23 companies who are involved in the creation and maintenance of databases.
We asked these executives, "What are the keys to a successful database strategy?" Here's what they told us:
Tarantool vs. Redis: In-Memory Databases Face Off
With respect to in-memory databases, Redis improved upon Memcached with the abilities it introduced to persist cached data, to use data types other than strings, and to perform complex operations on data. [1]
Tarantool improves upon Redis by taking the operations that can be performed on data sets to a whole new level of sophistication—as well as surpassing Redis in terms of persistence and indexing, not to mention speed and support. [2] In fact, given the high quality of Tarantool’s persistence processes, as well as its facility for transactions and large data sets, it can effectively be used as an application’s sole database—a feat that is frankly not often accomplished with Redis. [3]
Developing a User Profile Store With Golang and a NoSQL Database
Remember the tutorial series I wrote in regards to creating a user profile store with Node.js and NoSQL? That tutorial covered a lot of ground, from creating a RESTful API with Node.js, handling user sessions to data modeling and storing data associated with users.
What if we wanted to take the same concepts and apply them with Golang instead of JavaScript with Node.js?
Fun With SQL: Functions in Postgres
DZone Database Zone Fun With SQL: Functions in Postgres In our previous Fun with SQL post on the Citus Data blog, we covered w...
-
DZone Database Zone Fun With SQL: Functions in Postgres In our previous Fun with SQL post on the Citus Data blog, we covered w...
-
DZone Database Zone Building a Boolean Logic Rules Engine in Neo4j A boolean logic rules engine was the first project I did for N...
-
DZone Database Zone MongoDB Indexes With Spring Data When working with large amounts of data, the use of indexes will greatly impro...