Spawn (@Spawn_Db) header
Spawn (@Spawn_Db) profile picture

On demand databases for development and CI workflows. We're looking for users for beta testing and co-design. #devops #database #kubernetes #docker

Cambridge, UK
Joined September 2020
📽️📽️ Check out how @cjheppell demos Spawn and explains how to unlock database testing in #CI with Spawn youtube.com/watch?v=sxHtca85… #database #devops #CICD
1
It's our last working day of 2020 so here's the end of year summary we've all been waiting for! It's been great developing Spawn this year, can't wait to push it further in 2021, see you then! spawn.cc #devops #containers #SoftwareEngineering #Kubernetes #dev
1
6
It's a new week, and we're still looking for Beta users. If you're looking to improve efficiency & productivity in your #devops process then get in touch at spawn.cc to sign up, and let's talk about how we can help. #kubernetes #databases
3
5
A consistent dataset is important in a team environment, but causes issues when the data size grows. Sharing data images with Spawn allows your team to be able to quickly create data containers, all from the same start point but isolated from each other's changes. #data #devops
1
2
1
Spawn #data containers give you read/write access to a database in seconds, data included. Create them using a single command. Learn more in our documentation here: spawn.cc/docs/howto-datacont… #containers #docker #kubernetes #devops
1
6
Spawn data images are like #Docker images, but for databases. Starting with one, you can instantly create as many running #databases as you like, all starting with exactly the same #data but completely isolated from one another. Set them up with just a couple of commands!
2
Amongst the in-depth documentation for Spawn spawn.cc/docs/getting-starte…) we're going to be including some simple "How to" guides to take you through the journey. The first might be self-explanatory, but it's the one you need to get started, so lets begin... More coming soon!
1
One thing we've heard a lot from people is that they get tired of tripping over team members in the same dev #database. Therefore empowering you to spin up your own clones was a key focus of Spawn from the start. Read more about it here: spawn.cc/docs/spawn-for-a-te… #development
1
3
Signing up to the Spawn #Beta is as simple as 1, 2, 3! A key aspect is a conversation at step 2. We really want to understand what you're up against, and hoping to achieve. Head over to spawn.cc to sign up, and let's talk :) #DevOps #kubernetes #databases
1
1
Step 4: Share with teams Each running #database copy is intended for a single user, but uploaded #databases and saved changes can be shared. Make sure your whole team has the best test #data available, & share any improvements. Make the same data available to your #CI pipelines.
1
2
Step 3: Work, save changes, undo them Snapshot the state of your #database at any time. Immediately undo large mistakes, or save changes to use as the starting point for new Db copies. New copies can be created at any time, so you're never in danger of damaging your database.
1
1