Crunchy Data

Whether you're building a custom mission application, or installing a commercial of the shelf software tool, your goal is to get it through ATO and into production quickly and reliably. That should influence how you start your project, especially when it comes to selecting the database you use. Make your ATO a non-event and build with an ATO ready database from the start. Join me today at 2pm EDT to see how Crunchy Postgres for Kubernetes is an ATO ready database. You'll learn how it addresses key mission readiness requirements like continuity of operations, high availability, and disaster recovery along with being able to automatically configure it according to the STIG. Build ATO ready applications. Build with Confidence. Build with Crunchy Postgres. Crunchy Data https://lnkd.in/gjqEFHgE

Most people look at a pricing calculator and compare the same resources to the same resources then decide which is cheaper. The reality is not all providers are equal. Some come with #Postgres much more tuned for production workloads. Some architect their platform to deliver significant competitive advantages. While this is not news to me, we've been doing this Crunchy Data for a number of years. I'm still often surprised each time I see the different in performance numbers. You Need a Budget migrated from Heroku. Got 30% increase in their IOPS at the same time as a 10% price reduction. https://lnkd.in/gGuahNhD Nifty migrated from Amazon Aurora. The result 50% decrease in monthly cost for more predictable performance. https://lnkd.in/gZq3QyzB Calibre Analytics migrated from Heroku, in large part because they wanted a better support experience. But it also came with a pleasant surprise that for the same cost they got a 20% performance improvement. https://lnkd.in/g9EvRwMm CareRev migrated to us after heavily evaluating RDS and having some RDS footprint. The result 10% cost savings, 40% increase in IOPS. They still have some straggling RDS instances, their team emails is out of the blue just to let us know that their Crunchy Bridge databases are the ones that just work and the team doesn't have to babysit, they can't wait until the rest are migrated. I think you get the idea at this point... 

Most people look at a pricing calculator and compare the same resources to the same resources then decide which is cheaper. The reality is not all providers are equal. Some come with #Postgres much more tuned for production workloads. Some architect their platform to deliver significant competitive advantages. While this is not news to me, we've been doing this Crunchy Data for a number of years. I'm still often surprised each time I see the different in performance numbers. You Need a Budget migrated from Heroku. Got 30% increase in their IOPS at the same time as a 10% price reduction. https://lnkd.in/gGuahNhD Nifty migrated from Amazon Aurora. The result 50% decrease in monthly cost for more predictable performance. https://lnkd.in/gZq3QyzB Calibre Analytics migrated from Heroku, in large part because they wanted a better support experience. But it also came with a pleasant surprise that for the same cost they got a 20% performance improvement. https://lnkd.in/g9EvRwMm CareRev migrated to us after heavily evaluating RDS and having some RDS footprint. The result 10% cost savings, 40% increase in IOPS. They still have some straggling RDS instances, their team emails is out of the blue just to let us know that their Crunchy Bridge databases are the ones that just work and the team doesn't have to babysit, they can't wait until the rest are migrated. I think you get the idea at this point... 

Great notes on the state of spatial analytics from Matt Forrest 👏

A common question we get is what is our recommended editor for working with Postgres? This is a little like asking our favorite football team or favorite color. There isn't a wrong answer, it is largely a question of where you come from. Are you on Windows, Mac, Linux? Do you prefer integration with your code then vscode with some plugins. Do you want a GUI editor or are you a CLI person? But, there is one editor that almost everyone has when working with Postgres–the built-in CLI editor psql. Psql comes with Postgres already, and while it's a great editor on it's own with a few tips and tricks you can really get a lot more out of it. Take a read on how you can: * Format your query output * Auto display query run times * Easily preserve query history * Navigate your database schema * And much much more. https://lnkd.in/dGgdXMDm

Want to see Crunchy Postgres for Kubernetes in action? Sign up for our webinar on Aug. 27 and check out how it can quickly and reliably keep your database in security compliance. More details and registration right here: https://lnkd.in/gEzpU6Gw

Foreign tables within Postgres have always been a powerful concept, but as our team member Marco Slot slot describes - "they can be extremely tedious to work with because have to specify column names and types which is frustrating for something that already has its own column names and types." As we've worked to improve on the experience of working on Postgres this was one of our smaller but exciting advancements with Crunchy Bridge for Analytics. Now you can simply point at a CSV file and Postgres will auto-detect all of the column names and types, no more tedious mapping. Same goes for your Parquet or Iceberg files as well. Is it really that easy? Well here is: * Connecting to a CSV in S3 * Describing the newly created table * Querying the table All in a matter of seconds.

#PostGISDay 2024 Call for Papers is now open! We are looking for 20-25 minute talks on using PostGIS. We welcome case studies, tips and tricks, or anything PostGIS related. Feel free to submit several talk ideas if you have more than one! We look forward to reading through your proposals. https://lnkd.in/e5PQ5s4Z

Adam Timm digs into how Crunchy Postgres for Kubernetes delivers an “ATO ready” and secure Postgres experience for Kubernetes, enabling organizations to streamline and standardize their approach to securely configuring Postgres in Kubernetes in this article on Intelligence Community News. https://lnkd.in/euH6RAKZ

📢 Register for our Aug. 27 webinar to learn how to use Kubernetes to automate your Postgres STIG compliance and ATO workflows using Crunchy Postgres for Kubernetes! This is going to be a great conversation and opportunity to showcase how Crunchy Postgres for Kubernetes addresses specific challenges of secure data management in containerized environments. https://lnkd.in/ejBrrVTP