Manifold Acquisition and what it means for Existing Users
Manifold, one of the platforms that provides the JawsDB service, has been acquired. Please see their announcement below. Manifold customers will need to take action to keep their databases running and this process will be explained at the end of this announcement.
We are excited to announce that Manifold has been acquired by Snyk. Snyk’s cloud native application security platform empowers developers to build security seamlessly into their development process - across code, open source, containers and infrastructure as code. If you are a developer looking to solve security issues earlier in a dev-friendly way, we would encourage you to give Snyk a try.
The Manifold team will be helping accelerate the extensibility of Snyk’s platform, making it easier to build upon and automate existing developer workflows.
Unfortunately, this means that we are shutting down the Manifold Marketplace.
To give you plenty of time to migrate any active resources you manage with Manifold, we will keep the marketplace running until April 26, 2021. At that time, all Manifold-managed accounts, resources, and custom configurations will cease to function.
In order to keep Manifold users’ databases running, we can move their existing database to our other provider (Heroku) without any downtime. Such users must please perform the following steps.
If the user is already a Heroku customer, please begin at step 2.
If the user already has an application on Heroku where they wish to place the database server, please skip to step 3.
- Create an account on Heroku.com
- Create an ‘Application’ on Heroku where the database will be attached. This does not have to contain an actual application, it can be empty.
- Provision a NEW JawsDB database from the Heroku Elements Marketplace equivalent to the current database on Manifold *.
- Inform us of the MySQL username of the new database by sending an email to
email@example.com. JawsDB will replace the newly created database with the existing database on Manifold.
- AFTER JawsDB informs the user that the database has been successfully replaced. Users may cancel your JawsDB account with Manifold.
* Users with a custom plan on Manifold should please reach out to us at the support email so we can create an equivalent custom plan for them on Heroku
8.0 is now the default MySQL version on JawsDB
MySQL version 8.0 is now the default version of MySQL for all new provisions of JawsDB MySQL. Users currently on a 5.7 version database will experience no change at the present time.
Any users of single-tenant databases (Whitetip plans and higher) currently on version 5.7 can request an in-place upgrade to 8.0 at any time by sending a ticket through Heroku or by sending an email to support.
Multi-tenant servers providing service to those with Kitefin, Leopard, and Blacktip plans will be upgraded at a future date. Some of the 5.7 servers will remain at that version much longer for those who do not wish to make the upgrade.
New provisions for Heroku users can still be placed on MySQL 5.7 by adding a
--version flag to the provision request.
On the CLI
$ heroku addons:create jawsdb:PLANNAME -a HEROKUAPPNAME --version=5.7
JawsDB now supports MySQL Version 8.0
By popular request, we have added support for MySQL version 8.
Because many existing users rely on version 5 and have not updated their code to support MySQL 8, MySQL version 5.7 will remain the default for new provisions.
Users who wish to take advantage of version 8 can do so using one of the following methods.
New provisions on Heroku can be placed on MySQL 8.0 by adding a
--version flag to the provision request.
On the CLI
$ heroku addons:create jawsdb:PLANNAME -a HEROKUAPPNAME --version=8.0
Existing single-tenant users can also request that their current database be updated in-place to 8.0 via an email to support.
Single-tenant users on Manifold also can request that their existing database be updated in-place to 8.0. Please email support.
5.7 will remain the default for new provisions.
Impressive new features
MySQL 8 features improvements to INNODB, JSON enhancements, Common Table Expressions (CTEs), full regular expression support, window functions and more!
Come try it out!
Server Metrics Graphs Available
Users of single-tenant database plans (currently: Whitetip, Thresher, Tiger, Hammerhead, and Goblin), now have access to graphs of important database metrics for CPU, storage, and IO. They can be accessed through the dashboard on the ‘Server Status’ panel.
The metric data points are spaced 5-minutes apart and can be viewed for periods of:
- The last hour
- The last 3 hours
- The last day
- The last 3 days
- The last week
Below is a brief description of the included metrics.
- CPU Utilization - The percentage of the CPU in use.
- Read IOPS - The average number of Read-specific IO operations per second.
- Write IOPS - The average number of Write-specific IO operations per second.
- Free Storage - The free storage in GB for the server.
- Read Latency - The average time taken per read-specific IO operation on disk.
- Write Latency - The average time taken per write-specific IO operation on disk.
- Disk Queue Depth - The average number of outstanding IOs (read/write requests) waiting to access the disk.
- Network Transmit Throughput - The outgoing network traffic on the server in MB.
- Network Receive Throughput - The incoming network traffic on the server in MB.
These descriptions as well as greater detail about how to interpret them will be in the documentation.
Databites can now be shared publicly
As Christmas approaches, we wanted to deliver on one more commonly requested addition to the service!
Databites are a feature of JawsDB where a read-only query can be run against a user’s database directly from their dashboard and saved for future viewing. Commonly created Databites include those that track used storage space, company sales over time, user engagement with blog posts, etc.
Before today, Databites were only viewable by the owner of the JawsDB instance with access to that instance’s dashboard. Now, a Databite’s creator can choose to mark individual Databites as public. Doing so will generate a URL which can be shared publicly. Those with the link can view the Databite in their own browser without needing to log into Heroku or any other service. The query used to generate the Databite will be hidden, but the output will display as it does for the logged-in owner of the Databite.
Thank you all for your support and feedback this year. We look forward to even greater changes and updates to JawsDB in days to come.
Merry Christmas, and Happy Holidays!
Snapshots (Backups) now Restorable on Demand
The number one feature requested by users is greater control over backups for their server. JawsDB takes daily backups of every server and holds on to them for a pre-determined length of time depending on which plan the user has purchased. What’s different about JawsDB backups is we take a snapshot of the entire server as it existed at that point in time; these are not just SQL dumps of a server’s data. While there are many benefits to this approach, it has made it difficult to share these backups with users who may want them to restore to an earlier point in time or for copying their database elsewhere.
Today, we are happy to announce that this is changing. Users of single-tenant instances (Whitetip and higher) will now be shown a list of JawsDB’s held snapshots on their dashboard page along with information about what exact time the snapshot was taken. There is also a new section that will allow a JawsDB user to restore ANY snapshot that they have access to. This is not limited to the snapshots for that given JawsDB instance! Users who wish to restore a snapshot they own to a completely new JawsDB instance may do so through this new feature. Details and examples can be found in our Documentation
Thank you all who have submitted feedback and who have requested this feature. Stay tuned for more enhancements to snapshots. We hope to add the ability for users to take a snapshot manually off-schedule for later restoration.
JawsDB MySQL now Generally Available
After a successful early access period we’re proud to announce that our MySQL service is now generally available to all customers. During our time operating as an add-on in Heroku’s Marketplace, we’ve had many customers ask for a way to enjoy the convenience of our add-on while maintaining the freedom to deploy their app to any platform of their choosing, such as Azure, AWS, etc. By working together with Manifold, we are excited to provide the simplicity of one-click MySQL wherever our customers choose to host their app.
Adding to this exciting news we will also be offering MariaDB and PostgreSQL in the coming weeks as well as more robust plans for all of our services. We’re also looking into offering new regions dependent on customer demand, so we welcome you to reach out via Twitter or email if you have any questions or requests.
JawsDB in Early Access, powered by Manifold
Today we’re excited to announce the availability of JawsDB as a standalone database service. Until now, the service has only been available to Heroku customers. Starting today you will be able to create a JawsDB database for use with any of your applications, on any host or platform.
For the Early Access period we’re offering a subset of our standard plans: three shared and three single tenant plans across the US East and EU West regions. We will be rolling out the rest of our plans, including our popular High Availability plans, as we get closer to General Availability.
We’ve partnered with Manifold to make our service cloud agnostic. You will be able to use your Manifold account to create and modify your JawsDB databases, receiving one convenient bill.
If you have any questions or require support feel free to reach out via our normal support channels.